From: Nishanth Menon <nm@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Raghavendra, Vignesh" <vigneshr@ti.com>, <tony@atomide.com>,
<kristo@kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>
Subject: Request: Add Transition TI Tree to linux-next
Date: Sat, 20 Nov 2021 21:25:48 -0600 [thread overview]
Message-ID: <20211121032548.c56zt66ac5hjbu7j@garden> (raw)
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
Hi Stephen,
We have been working towards a rotating maintainership for various
TI dts and potentially related areas that Santosh is currently
maintaining. As part of this, my tree[1] is now integrated into the
common effort.
Please replace my current tree[1] with:
git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git#ti-next
We will follow the usual rules (GPLv2, contributer's guidelines,
reviews, successfully tested, meant for next merge window and intent
towards linus's tree via submaintainers) and this would be a rebased
tree as needed.
[1]
git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git#ti-k3-next (ti-k3-new)
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-11-21 3:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 3:25 Nishanth Menon [this message]
2021-11-22 22:10 ` Request: Add Transition TI Tree to linux-next Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2020-08-19 12:11 Nishanth Menon
2020-08-19 22:15 ` 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=20211121032548.c56zt66ac5hjbu7j@garden \
--to=nm@ti.com \
--cc=kristo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.com \
/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).