From: Linus Torvalds <torvalds@linux-foundation.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Dipen Patel <dipenp@nvidia.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-tegra <linux-tegra@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] hte: New subsystem for v5.19-rc1
Date: Fri, 3 Jun 2022 21:37:58 -0700 [thread overview]
Message-ID: <CAHk-=wiVxF5VLFSuet3OrC7u1Gfb-ZyMs4W-KXAc42rXPRWmhA@mail.gmail.com> (raw)
In-Reply-To: <20220603113908.78777-1-thierry.reding@gmail.com>
On Fri, Jun 3, 2022 at 4:39 AM Thierry Reding <thierry.reding@gmail.com> wrote:
>
> Note that this currently supports only one provider, but there seems to
> be enough interest in this functionality and we expect to see more
> drivers added once this is merged.
So the "one provider" worries me, but the part that really doesn't
make me all warm and fuzzy is how this came in at the end of the merge
window.
And it's a bit odd in other ways.
The DT bindings got the comment "why call it 'hardware timestamp'"
when no other case seems sane.
So the DT bindings got renamed. So now part of the code calls it "hte"
(which nobody understands outside of the hte community that is
apparently one single device: Tegra) and part of the code calls it
"timestamp".
Hmm.
Linus
next prev parent reply other threads:[~2022-06-04 4:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 11:39 [GIT PULL] hte: New subsystem for v5.19-rc1 Thierry Reding
2022-06-04 4:37 ` Linus Torvalds [this message]
2022-06-04 8:11 ` Linus Walleij
2022-06-05 16:16 ` Linus Torvalds
2022-06-05 16:32 ` Thierry Reding
2022-06-16 18:30 ` Dipen Patel
2022-06-05 16:27 ` Thierry Reding
2022-06-05 17:16 ` pr-tracker-bot
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='CAHk-=wiVxF5VLFSuet3OrC7u1Gfb-ZyMs4W-KXAc42rXPRWmhA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=bgolaszewski@baylibre.com \
--cc=dipenp@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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).