From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k•org>
Cc: Linux-Next <linux-next@vger•kernel.org>,
Linux-Renesas <linux-renesas-soc@vger•kernel.org>
Subject: Re: New Renesas SoC tree for linux-next (was: [PATCH] MAINTAINERS: Add Geert as Renesas SoC Co-Maintainer)
Date: Wed, 31 Jul 2019 22:15:50 +1000 [thread overview]
Message-ID: <20190731221550.5be0a103@canb.auug.org.au> (raw)
In-Reply-To: <CAMuHMdV1zXCq6dbcg6=YmHgYqE5tfc1e7DbB3UgTVPm-5rU2Bw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2318 bytes --]
Hi Geert,
On Wed, 31 Jul 2019 09:33:19 +0200 Geert Uytterhoeven <geert@linux-m68k•org> wrote:
>
> Apparently Gmail marked my previous email as spam, so probably that's
> why I don't see my branch in linux-next.
Nothing to do with Gmail, just me not reading well enough. Sorry about
that.
> Can you please add it?
Will do.
> Stephen: Can you please add my branch to linux-next, after Simon's
> branch, which may still receive fixes for v5.3?
>
> ARM/RENESAS ARM64 ARCHITECTURE
> M: Simon Horman <horms@verge•net.au>
> +M: Geert Uytterhoeven <geert+renesas@glider•be>
> M: Magnus Damm <magnus.damm@gmail•com>
> L: linux-renesas-soc@vger•kernel.org
> Q: http://patchwork.kernel.org/project/linux-renesas-soc/list/
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
> next
>
> ARM/SHMOBILE ARM ARCHITECTURE
> M: Simon Horman <horms@verge•net.au>
> +M: Geert Uytterhoeven <geert+renesas@glider•be>
> M: Magnus Damm <magnus.damm@gmail•com>
> L: linux-renesas-soc@vger•kernel.org
> Q: http://patchwork.kernel.org/project/linux-renesas-soc/list/
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
> next
Added from tomorrow.
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:[~2019-07-31 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190729175658.13672-1-geert+renesas@glider.be>
2019-07-31 7:33 ` New Renesas SoC tree for linux-next (was: [PATCH] MAINTAINERS: Add Geert as Renesas SoC Co-Maintainer) Geert Uytterhoeven
2019-07-31 12:15 ` Stephen Rothwell [this message]
2019-08-01 7:26 ` Geert Uytterhoeven
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=20190731221550.5be0a103@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=geert@linux-m68k$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-renesas-soc@vger$(echo .)kernel.org \
/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