From: Hans de Goede <hdegoede@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
"David E. Box" <david.e.box@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>
Cc: Andy Shevchenko <andy@infradead.org>,
Mark Gross <mark.gross@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] platform-drivers-x86 for 5.11-1
Date: Wed, 13 Jan 2021 10:21:36 +0100 [thread overview]
Message-ID: <5c87fbd3-b4f1-2d1b-3058-0d2c57cc983a@redhat.com> (raw)
In-Reply-To: <c24d791c-1f2f-7f94-84cd-450cbdba6ce3@redhat.com>
Hi,
On 12/16/20 10:21 AM, Hans de Goede wrote:
> Hi,
>
> On 12/16/20 1:17 AM, Linus Torvalds wrote:
>> On Mon, Dec 14, 2020 at 4:43 AM Hans de Goede <hdegoede@redhat.com> wrote:
>>>
>>> - New Intel PMT telemetry and crashlog drivers
>>
>> These have _very_ annoying Kconfig setups.
>>
>> First it asks about INTEL_PMT support.
>>
>> If you say no, it then asks about INTEL_PMT_CLASS, INTEL_PMT_TELEMETRY
>> and INTEL_PMT_CRASHLOG support.
>
> Yeah that is bad, sorry for not spotting that (I answer M/Y everywhere
> so that I at least compile test everything).
>
>> I've pulled this,
>
> Thanks.
>
>> but I really wish the PMT support understood that
>> whole "No means no" thing.
>
> Agreed. I will make sure to get a fix to you for this sometime
> during the 5.11 cycle.
>
> Alexander and/or David I believe that the best solution for this
> would be to replace the:
>
> select INTEL_PMT_CLASS
>
> In the INTEL_PMT_TELEMETRY and INTEL_PMT_CRASHLOG Kconfig entries
> with "depends on". Also as a general comment for the future, select
> should typically be used with non-user-selectable options. E.g.
> you could also have made INTEL_PMT_CLASS non-user-selectable by
> changing:
>
> config INTEL_PMT_CLASS
> tristate "Intel Platform Monitoring Technology (PMT) Class driver"
>
> To:
>
> config INTEL_PMT_CLASS
> tristate
>
> Having both INTEL_PMT_CLASS user-selectable and using select on
> it is bad. I believe that in this case changing the 2 "select"-s
> to "depend on"-s is best.
Alexander and/or David can you please write and submit a fix for this soon?
Thanks & Regards,
Hans
next prev parent reply other threads:[~2021-01-13 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 12:43 Hans de Goede
2020-12-16 0:17 ` Linus Torvalds
2020-12-16 9:21 ` Hans de Goede
2021-01-13 9:21 ` Hans de Goede [this message]
2020-12-16 1:00 ` 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=5c87fbd3-b4f1-2d1b-3058-0d2c57cc983a@redhat.com \
--to=hdegoede@redhat.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=andy@infradead.org \
--cc=david.e.box@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®