public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: <Conor.Dooley@microchip.com>
Cc: <palmer@rivosinc.com>, <linux-riscv@lists.infradead.org>,
	<linux-next@vger.kernel.org>, <Daire.McNamara@microchip.com>
Subject: Re: Please add Microchip RISC-V branches to linux-next
Date: Tue, 7 Jun 2022 08:51:28 +1000	[thread overview]
Message-ID: <20220607085128.58e003ed@canb.auug.org.au> (raw)
In-Reply-To: <5ecd9c16-ce86-3666-3c2d-a14218659d79@microchip.com>

[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]

Hi Conor,

On Mon, 6 Jun 2022 22:06:19 +0000 <Conor.Dooley@microchip.com> wrote:
>
> To take some work off Palmer's shoulders, I am going to send him
> PRs for "my" (Microchip RISC-V) device trees going forwards.
> 
> Could you please add the following branches to linux-next?
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ dt-for-next
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ dt-fixes
> 
> I had a quick look on lore, but couldn't easily see an example
> of someone requesting a tree that goes via Arnd etc, so in case
> it is relevant that the PRs will be to Palmer rather than Linus,
> my branches are aimed at
> https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/ for-next
> &
> https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/ fixes
> respectively.
> 
> Please let me know if you need any more info,

Thats perfect, thanks.

Added from today.  I have called them risc-v-mc and risc-v-mc-fixes in
linux-next.

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

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-06-06 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 22:06 Please add Microchip RISC-V branches to linux-next Conor.Dooley
2022-06-06 22:51 ` Stephen Rothwell [this message]
2022-06-07  6:27   ` Conor.Dooley

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=20220607085128.58e003ed@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Conor.Dooley@microchip.com \
    --cc=Daire.McNamara@microchip.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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