From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Michael Ellerman <mpe@ellerman•id.au>
Cc: maddy@linux•ibm.com, linuxppc-dev@lists•ozlabs.org,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Andrew Donnellan <ajd@linux•ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle•com>
Subject: Re: Please add powerpc topic/cxl branch to linux-next
Date: Tue, 18 Mar 2025 00:26:43 +1100 [thread overview]
Message-ID: <20250318002643.71ef29f1@canb.auug.org.au> (raw)
In-Reply-To: <87y0x3dibs.fsf@mpe.ellerman.id.au>
[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]
Hi Michael,
On Mon, 17 Mar 2025 22:09:43 +1100 Michael Ellerman <mpe@ellerman•id.au> wrote:
>
> Could you please add the topic/cxl branch of the powerpc tree to
> linux-next for the next few weeks, it's targeted for the next merge
> window.
>
> https://web.git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/log/?h=topic/cxl
Translated to git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git#topic/cxl
:-)
> It contains a topic branch of sorts to hold the cxl removal. It has a
> few commits from the SCSI tree, up to and including the cxlflash
> removal, then it merges powerpc/fixes to get a Documentation/ patch that
> touches cxl, and then the cxl removal patch from Andrew.
>
> The plan will be to send it to Linus after the powerpc and SCSI trees
> have been merged, during the merge window.
OK, added from later today. I have added it late in the merges. Let me
know when you are finished with it.
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@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-03-17 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 11:09 Please add powerpc topic/cxl branch to linux-next Michael Ellerman
2025-03-17 13:26 ` Stephen Rothwell [this message]
2025-04-03 2:32 ` Michael Ellerman
2025-04-03 6:29 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250318002643.71ef29f1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=ajd@linux$(echo .)ibm.com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maddy@linux$(echo .)ibm.com \
--cc=martin.petersen@oracle$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox