[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230211115558.393dfc85@canb.auug.org.au>
Date: Sat, 11 Feb 2023 11:55:58 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Lorenzo Pieralisi <lpieralisi@...nel.org>,
Krzysztof Wilczyński
<kw@...ux.com>, Linus Torvalds <torvalds@...ux-foundation.org>,
linux-next@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Update PCI git tree location for linux-next
Hi Bjorn,
On Mon, 6 Feb 2023 10:29:45 -0600 Bjorn Helgaas <helgaas@...nel.org> wrote:
>
> On Mon, Feb 06, 2023 at 07:53:37AM +1100, Stephen Rothwell wrote:
> >
> > All done. Do you want any contacts for this tree added to my list?
>
> Yes, please! Can you add:
>
> Lorenzo Pieralisi <lpieralisi@...nel.org>
> Krzysztof Wilczyński <kw@...ux.com>
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.
--
Cheers,
Stephen Rothwell
sfr@...b.auug.org.au
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists