From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dipen Patel <dipenp@nvidia.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-next@vger.kernel.org
Subject: HTE tree for linux-next
Date: Tue, 3 May 2022 14:57:14 +0200 [thread overview]
Message-ID: <YnEmqsfZu7uWsm8s@orome> (raw)
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
Hi Stephen,
Dipen has been working on a new subsystem for hardware timestamping and
Linus Walleij suggested to put it in linux-next to give it a bit of soak
time before we propose it for inclusion in mainline.
To simplify things, I've pushed a branch with the patches to the Tegra
repository for now, but longer term the plan is to get Dipen set up with
the necessary keys to maintain this in a separate tree.
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git#hte/for-next
Can you add this to the list of trees for linux-next?
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-05-03 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 12:57 Thierry Reding [this message]
2022-05-03 21:46 ` HTE tree for linux-next 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=YnEmqsfZu7uWsm8s@orome \
--to=thierry.reding@gmail.com \
--cc=dipenp@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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