Update PCI git tree location for linux-next
Subsystems (2)
Hi Stephen,
Can you please replace this PCI tree:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
with this new shared one:
git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git
The branch names intended for linux-next ("for-linus" and "next") are staying the same.
Thanks,
Bjorn
Hi Bjorn,
Quoted 5 lines · On Fri, 3 Feb 2023 16:27:05 -0600 Bjorn Helgaas <[email protected]> wrote:
Hi Stephen,
Can you please replace this PCI tree:
Quoted 8 lines
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.gitwith this new shared one:
git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.gitThe branch names intended for linux-next ("for-linus" and "next") are staying the same.
All done. Do you want any contacts for this tree added to my list?
Signature · 2 lines
Cheers, Stephen Rothwell
Quoted 10 lines · Stephen Rothwell
Hi Bjorn,
Quoted 7 lines · On Fri, 3 Feb 2023 16:27:05 -0600 Bjorn Helgaas <[email protected]> wrote:
Hi Stephen,
Can you please replace this PCI tree:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
Quoted 8 lines
Quoted 6 lines
with this new shared one:
git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.gitThe branch names intended for linux-next ("for-linus" and "next") are staying the same.
All done. Do you want any contacts for this tree added to my list?
Yes, please! Can you add:
Lorenzo Pieralisi <[email protected]>
Krzysztof Wilczyński <[email protected]>
Thanks,
Bjorn
Hi Bjorn,
Quoted 9 lines · On Mon, 6 Feb 2023 10:29:45 -0600 Bjorn Helgaas <[email protected]> wrote:
Quoted 2 lines · Stephen Rothwell
All done. Do you want any contacts for this tree added to my list?
Yes, please! Can you add:
Lorenzo Pieralisi <[email protected]>
Krzysztof Wilczyński <[email protected]>
Now added, sorry for the delay.
For Lorenzo's and Krzysztof's benefit:
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 · 7 lines
Cheers, Stephen Rothwell [email protected] -- Cheers, Stephen Rothwell