archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <>
To: Linus Torvalds <>
Cc: Linus Walleij <>,
	"D, Lakshmi Sowjanya" <>,
	Dipen Patel <>,
	Bartosz Golaszewski <>,
	linux-tegra <>,
	Linux Kernel Mailing List <>,
	Mark Gross <>,
	Andy Shevchenko <>,
	"Saha, Tamal" <>,
Subject: Re: [GIT PULL] hte: New subsystem for v5.19-rc1
Date: Sun, 5 Jun 2022 18:32:11 +0200	[thread overview]
Message-ID: <Ypzai+P9BIVhHT7t@orome> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

On Sun, Jun 05, 2022 at 09:16:21AM -0700, Linus Torvalds wrote:
> On Sat, Jun 4, 2022 at 1:11 AM Linus Walleij <> wrote:
> >
> > Another provider did come up, and were requested (by me) to work with
> > Dipen on the subsystem in august last year, that was the Intel PMC in the
> > Elkhart and Tiger Lake platforms and forward
> Ok, I've pulled this now, even if I don't love the "hte" name. I
> despise specialized TLA's that aren't some obvious "if you're a kernel
> developer, you know what this means".

Thanks. If you prefer we could follow up with a rename for v5.20 and
name this similar to the device tree bindings. There are other cases
where the device tree bindings are named differently from the Linux
subsystem and/or driver directories, but admittedly it'd be easy to
make them match in this case. Given how little this is exposed at
this point, renaming should be fairly unintrusive.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-06-05 16:32 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
2022-06-04  8:11   ` Linus Walleij
2022-06-05 16:16     ` Linus Torvalds
2022-06-05 16:32       ` Thierry Reding [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Ypzai+P9BIVhHT7t@orome \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).