From: "Arnd Bergmann" <arnd@arndb.de>
To: "Bart Van Assche" <bvanassche@acm.org>,
"Russell King" <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: riscpc: Unbreak the build
Date: Fri, 09 Sep 2022 08:25:00 +0200 [thread overview]
Message-ID: <250f66b4-5b12-4e5f-94df-b65b1f5c386b@www.fastmail.com> (raw)
In-Reply-To: <50c28c4a-b62b-9258-3b0d-3d5de85154b0@acm.org>
On Thu, Sep 8, 2022, at 10:45 PM, Bart Van Assche wrote:
> On 9/8/22 13:38, Russell King (Oracle) wrote:
>> That'll do. Please put it in the patch system, and I'll get to it maybe
>> next week sometime. Thanks.
>
> Hi Russell,
>
> Can you please clarify what "put it in the patch system" means? I'm familiar
> with the email based workflow but not with any other workflow for submitting
> kernel patches.
See https://www.arm.linux.org.uk/developer/patches/info.php
for the process. You can use something like
git send-email --add-header=\"KernelVersion: $(git describe --abbrev=0)\" --to="patches@arm.linux.org.uk"
to add a patch there, and check the status in
https://www.arm.linux.org.uk/developer/patches/section.php?section=0
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-09 6:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 20:34 [PATCH] ARM: riscpc: Unbreak the build Bart Van Assche
2022-09-08 20:38 ` Russell King (Oracle)
2022-09-08 20:45 ` Bart Van Assche
2022-09-09 6:25 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-12 22:13 Bart Van Assche
2022-09-12 21:59 Bart Van Assche
2022-08-30 19:55 Bart Van Assche
2022-08-30 19:58 ` Russell King (Oracle)
2022-08-30 20:55 ` Bart Van Assche
2022-08-30 21:27 ` Russell King (Oracle)
2022-08-31 7:33 ` Arnd Bergmann
2022-08-31 20:56 ` Arnd Bergmann
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=250f66b4-5b12-4e5f-94df-b65b1f5c386b@www.fastmail.com \
--to=arnd@arndb.de \
--cc=bvanassche@acm.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).