From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Nishanth Menon <nm@ti•com>
Cc: Tero Kristo <t-kristo@ti•com>, <linux-next@vger•kernel.org>,
<linux-kernel@vger•kernel.org>
Subject: Re: Request: Add Transition TI Tree to linux-next
Date: Thu, 20 Aug 2020 08:15:07 +1000 [thread overview]
Message-ID: <20200820081507.04eb71a0@canb.auug.org.au> (raw)
In-Reply-To: <20200819121137.4v3rfabbrleohoc7@akan>
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
Hi all,
On Wed, 19 Aug 2020 07:11:37 -0500 Nishanth Menon <nm@ti•com> wrote:
>
> Could you add my ti-k3-next branch to linux-next? You can find it
> here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git#ti-k3-next
>
> NOTE: This tree will eventually supersede Tero's tree[1] which is
> currently in linux-next.
Added from today. I have called it ti-k3-new for now.
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:[~2020-08-19 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 12:11 Request: Add Transition TI Tree to linux-next Nishanth Menon
2020-08-19 22:15 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-21 3:25 Nishanth Menon
2021-11-22 22:10 ` 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=20200820081507.04eb71a0@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nm@ti$(echo .)com \
--cc=t-kristo@ti$(echo .)com \
/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