From: <Conor.Dooley@microchip•com>
To: <sfr@canb•auug.org.au>
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 06:27:56 +0000 [thread overview]
Message-ID: <4de48549-5382-f4ba-20c8-af7699c327b8@microchip.com> (raw)
In-Reply-To: <20220607085128.58e003ed@canb.auug.org.au>
On 06/06/2022 23:51, Stephen Rothwell wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 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.
That's great, thanks!
Conor.
prev parent reply other threads:[~2022-06-07 6:28 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
2022-06-07 6:27 ` Conor.Dooley [this message]
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=4de48549-5382-f4ba-20c8-af7699c327b8@microchip.com \
--to=conor.dooley@microchip$(echo .)com \
--cc=Daire.McNamara@microchip$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=palmer@rivosinc$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.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