-
Notifications
You must be signed in to change notification settings - Fork 48
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Automatic merge of 'master' into merge-test (2024-10-18 12:07)
- Loading branch information
Showing
175 changed files
with
2,222 additions
and
1,011 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,10 +30,13 @@ tree as a dedicated branch covering multiple subsystems. | |
The main SoC tree is housed on git.kernel.org: | ||
https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/ | ||
|
||
Maintainers | ||
----------- | ||
|
||
Clearly this is quite a wide range of topics, which no one person, or even | ||
small group of people are capable of maintaining. Instead, the SoC subsystem | ||
is comprised of many submaintainers, each taking care of individual platforms | ||
and driver subdirectories. | ||
is comprised of many submaintainers (platform maintainers), each taking care of | ||
individual platforms and driver subdirectories. | ||
In this regard, "platform" usually refers to a series of SoCs from a given | ||
vendor, for example, Nvidia's series of Tegra SoCs. Many submaintainers operate | ||
on a vendor level, responsible for multiple product lines. For several reasons, | ||
|
@@ -43,14 +46,43 @@ MAINTAINERS file. | |
|
||
Most of these submaintainers have their own trees where they stage patches, | ||
sending pull requests to the main SoC tree. These trees are usually, but not | ||
always, listed in MAINTAINERS. The main SoC maintainers can be reached via the | ||
alias [email protected] if there is no platform-specific maintainer, or if they | ||
are unresponsive. | ||
always, listed in MAINTAINERS. | ||
|
||
What the SoC tree is not, however, is a location for architecture-specific code | ||
changes. Each architecture has its own maintainers that are responsible for | ||
architectural details, CPU errata and the like. | ||
|
||
Submitting Patches for Given SoC | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
All typical platform related patches should be sent via SoC submaintainers | ||
(platform-specific maintainers). This includes also changes to per-platform or | ||
shared defconfigs (scripts/get_maintainer.pl might not provide correct | ||
addresses in such case). | ||
|
||
Submitting Patches to the Main SoC Maintainers | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
The main SoC maintainers can be reached via the alias [email protected] only in | ||
following cases: | ||
|
||
1. There are no platform-specific maintainers. | ||
|
||
2. Platform-specific maintainers are unresponsive. | ||
|
||
3. Introducing a completely new SoC platform. Such new SoC work should be sent | ||
first to common mailing lists, pointed out by scripts/get_maintainer.pl, for | ||
community review. After positive community review, work should be sent to | ||
[email protected] in one patchset containing new arch/foo/Kconfig entry, DTS | ||
files, MAINTAINERS file entry and optionally initial drivers with their | ||
Devicetree bindings. The MAINTAINERS file entry should list new | ||
platform-specific maintainers, who are going to be responsible for handling | ||
patches for the platform from now on. | ||
|
||
Note that the [email protected] is usually not the place to discuss the patches, | ||
thus work sent to this address should be already considered as acceptable by | ||
the community. | ||
|
||
Information for (new) Submaintainers | ||
------------------------------------ | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1761,8 +1761,8 @@ F: include/uapi/linux/if_arcnet.h | |
ARM AND ARM64 SoC SUB-ARCHITECTURES (COMMON PARTS) | ||
M: Arnd Bergmann <[email protected]> | ||
M: Olof Johansson <[email protected]> | ||
M: [email protected] | ||
L: [email protected] (moderated for non-subscribers) | ||
L: [email protected] | ||
S: Maintained | ||
P: Documentation/process/maintainer-soc.rst | ||
C: irc://irc.libera.chat/armlinux | ||
|
@@ -16086,6 +16086,7 @@ F: include/uapi/linux/net_dropmon.h | |
F: net/core/drop_monitor.c | ||
|
||
NETWORKING DRIVERS | ||
M: Andrew Lunn <[email protected]> | ||
M: "David S. Miller" <[email protected]> | ||
M: Eric Dumazet <[email protected]> | ||
M: Jakub Kicinski <[email protected]> | ||
|
@@ -21777,8 +21778,8 @@ F: drivers/accessibility/speakup/ | |
SPEAR PLATFORM/CLOCK/PINCTRL SUPPORT | ||
M: Viresh Kumar <[email protected]> | ||
M: Shiraz Hashim <[email protected]> | ||
M: [email protected] | ||
L: [email protected] (moderated for non-subscribers) | ||
L: [email protected] | ||
S: Maintained | ||
W: http://www.st.com/spear | ||
F: arch/arm/boot/dts/st/spear* | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.