From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for Jul 13
Date: Wed, 14 Jul 2021 08:41:06 +1000 [thread overview]
Message-ID: <20210714084106.0525b879@canb.auug.org.au> (raw)
In-Reply-To: <CAMuHMdUb_VvjGZUsnKuGpSwQfJMa0pqQ-tN5HCwi_-Am7angJw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
Hi Geert,
On Tue, 13 Jul 2021 10:44:40 +0200 Geert Uytterhoeven <geert@linux-m68k•org> wrote:
>
> I've just noticed you don't have
>
> renesas-fixes git
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git#fixes
>
> included yet. Can you please add it?
> This branch contains fixes intended for the current release.
Added from today.
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:[~2021-07-13 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 8:03 linux-next: Tree for Jul 13 Stephen Rothwell
2021-07-13 8:44 ` Geert Uytterhoeven
2021-07-13 22:41 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-13 2:37 Stephen Rothwell
2022-07-13 12:33 Stephen Rothwell
2020-07-13 9:25 Stephen Rothwell
2018-07-13 6:37 Stephen Rothwell
2017-07-13 3:23 Stephen Rothwell
2016-07-13 6:47 Stephen Rothwell
2015-07-13 4:17 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=20210714084106.0525b879@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=geert@linux-m68k$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@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