How to include a new branch in linux-next
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hi Tzung-Bi,
Quoted 36 lines · On Wed, 26 Jul 2023 15:10:28 +0800 Tzung-Bi Shih <[email protected]> wrote:
Quoted 15 lines · Stephen Rothwell
Quoted 7 lines · On Wed, 26 Jul 2023 14:27:48 +0800 Tzung-Bi Shih <[email protected]> wrote:
We are adding a new branch "for-firmware-next"[1] for chrome-platform-firmware.
I am wondering if linux-next has metadata repo so that I could send patches to include the newly created branch in linux-next.
Quoted 6 lines
I failed to find the repo thus I thought it has some discovery mechanisms. However, just realized the latest next-20230726[2] doesn't include "for-firmware-next".
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git/log/?h=for-firmware-next
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=0ba5d07205771c50789fd9063950aa75e7f1183fQuoted 6 lines
To get a branch added to linux-next, you just send me an email with the git URL for the branch, the email addresses of people (and/or mailing lists) who should be notified if there are any issues with the branch (like conficts, or build warnings etc) and an indication os what will be in the branch and how it will get to Linus Torvalds during the merge window.
Preferred name of the record:
chrome-platform-firmwareGIT URL:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git#for-firmware-nextEmail addresses if any issues with the branch:
<[email protected]>Mailing list:
<[email protected]>
Quoted 7 lines
What will be in the branch:
Changes fordrivers/firmware/google/which is mostly used for Google Chrome platform.Regarding PRs to Linus:
The same as chrome-platform[3] but it will use another name "chrome-platform-firmware".[3]: https://patchwork.kernel.org/project/chrome-platform/patch/ZJko2ipBSy8eM/[email protected]/
Added from today.
Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.
Signature · 3 lines
Cheers, Stephen Rothwell [email protected]