From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Ariel Simulevski <ariel@simulevski.at>
Cc: Guido Trentalancia <guido2022@trentalancia.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: tigerlake: Document supported platforms in Kconfig help
Date: Wed, 7 May 2025 19:05:01 +0300 [thread overview]
Message-ID: <aBuErZKeelnCaWbw@smile.fi.intel.com> (raw)
In-Reply-To: <CAMz-Jg-Vz9npxtVqjPXnK_WSDm2zc9_MBsQKTJKVghaSU7fyxg@mail.gmail.com>
On Mon, May 05, 2025 at 08:07:23PM +0200, Ariel Simulevski wrote:
> Hi Andy,
>
> Thanks for the feedback.
>
> Just to confirm: for the Kconfig help text, would you prefer keeping
> it strictly to a plain list of supported platforms (e.g. "Supported
> platforms: Tiger Lake, Alder Lake-N, Alder Lake-S") with no additional
> explanation or context?
Yes.
> And only PINCTRL_TIGERLAKE because I think
> that the note on PINCTRL_ALDERLAKE is actually quite helpful.
That note, about particular touchpad or touchscreen is confusing as
it is small part of the users that be hinted by it. The rest won't
understand why it is there. The driver runs on tons of different
platforms and configurations, so such a niche notices are not
applicable here.
> I want to make sure the v2 follows your expectations exactly.
Sure.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-05-07 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 18:07 [PATCH] pinctrl: tigerlake: Document supported platforms in Kconfig help Ariel Simulevski
2025-05-07 16:05 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-30 15:32 Ariel Simulevski
2025-04-30 18:14 ` Andy Shevchenko
2025-04-30 18:16 ` Andy Shevchenko
[not found] ` <CAMz-Jg-nNqUyzWpayBhPqhsGWOAKJPEa7uRWpOX0HWJDzqiQsg@mail.gmail.com>
2025-05-05 18:10 ` Andy Shevchenko
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=aBuErZKeelnCaWbw@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=ariel@simulevski.at \
--cc=guido2022@trentalancia.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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