From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, soc@kernel.org
Subject: Re: [GIT PULL 1/4] soc: driver updates for 6.11
Date: Tue, 16 Jul 2024 22:15:55 +0200 [thread overview]
Message-ID: <CACMJSetbuZ4u64fksB26AxMxYpiB2_i5=NJefDW_aN_-aHd62g@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wg+38EHPKGou1MqXwAAXC30cM8sMgZAGnZ7TcFO4L9J2w@mail.gmail.com>
On Tue, 16 Jul 2024 at 21:53, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Mon, 15 Jul 2024 at 13:59, Arnd Bergmann <arnd@arndb.de> wrote:
> >
> > soc: driver updates for 6.11
>
> Christ people, am I the only one actually testing any of this?
>
TBH it never occurred to me to test pure `make config`. I use `make
menuconfig` almost exclusively and never noticed this issue for that
reason.
> > Bartosz Golaszewski (14):
> > firmware: qcom: add a dedicated TrustZone buffer allocator
>
> This causes me to get a new and COMPLETELY NONSENSICAL question on my
> regular AMD Threadripper workstation config.
>
> I'm getting quite fed up with all the constant complete disregard for
> any sanity in Kconfig files. People are putting in COMPLETE GARBAGE
> here, and apparently nobody bothers to test it for any kind of sanity.
>
> This kind of crap needs to stop.
>
> I think the fix is to just add a
>
> depends on QCOM_TZMEM
>
> to that thing, but on my Altra machine even that doesn't fix this
> horror, because it turns out that everybody and their dog ends up
> doing
>
> select QCOM_SCM
>
> and we have QCOM_SCM doing
>
> select QCOM_TZMEM
>
> so it's hard as hell to actually get rid of that pointless churn,
> because you have to figure out which random driver ends up allegedly
> "needing" this.
>
> Are any of these actually _needed_? Because while I like automatic
> "select" things just picking the infrastructure that a driver actually
> requires to work, this all does *NOT* smell like "required
> infrastructure".
>
> This smells like random "do you actually want this?" to me.
>
> And the answer is "No. No I damn well do not". Particularly on my AMD
> machine that most definitely does not have some Qualcomm TrustZone
> thing.
>
> Linus
There's a patch from Geert already on the list[1] that should address this.
Bartosz
[1] https://lore.kernel.org/lkml/74947f7f132a811cc951749907b01bd25dcf23e6.1721135509.git.geert+renesas@glider.be/
next prev parent reply other threads:[~2024-07-16 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 21:03 [GIT PULL 0/4] soc tree for 6.11 Arnd Bergmann
2024-07-15 21:05 ` [GIT PULL 1/4] soc: driver updates " Arnd Bergmann
2024-07-16 19:25 ` pr-tracker-bot
2024-07-16 19:53 ` Linus Torvalds
2024-07-16 20:15 ` Bartosz Golaszewski [this message]
2024-07-16 20:34 ` Linus Torvalds
2024-07-16 20:49 ` Bartosz Golaszewski
2024-07-15 21:10 ` [GIT PULL 2/4] soc: dt " Arnd Bergmann
2024-07-16 18:55 ` Linus Torvalds
2024-07-16 19:33 ` Arnd Bergmann
2024-07-16 19:25 ` pr-tracker-bot
2024-07-15 21:11 ` [GIT PULL 3/4] soc: defconfig " Arnd Bergmann
2024-07-16 19:25 ` pr-tracker-bot
2024-07-15 21:12 ` [GIT PULL 4/4] soc: arm platform " Arnd Bergmann
2024-07-16 19:25 ` 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='CACMJSetbuZ4u64fksB26AxMxYpiB2_i5=NJefDW_aN_-aHd62g@mail.gmail.com' \
--to=bartosz.golaszewski@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).