archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <>
To: James Bottomley <>
Cc: Andrew Morton <>,
	linux-scsi <>,
	linux-kernel <>
Subject: Re: [GIT PULL] first round of SCSI updates for the 5.13+ merge window
Date: Fri, 2 Jul 2021 15:46:45 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Jul 2, 2021 at 1:11 AM James Bottomley
<> wrote:
> This series consists of the usual driver updates (ufs, ibmvfc,
> megaraid_sas, lpfc, elx, mpi3mr, qedi, iscsi, storvsc, mpt3sas) with
> elx and mpi3mr being new drivers.  The major core change is a rework to
> drop the status byte handling macros and the old bit shifted
> definitions and the rest of the updates are minor fixes.

Grr. I noticed this too late.

Why do we have that

        default y

for "config FC_APPID".

That makes absolutely zero sense to me. Not only don't we do "default
y" for new features _anyway_, but something like this is certainly
much too specialized to warrant it.

To make matters worse, it actually asks for this stupid thing *TWICE*.
Even if you say no the first time, it will then later on ask about
BLK_CGROUP_FC_APPID, and if you make the mistake to say 'y' on that
second try to push this feature, that will then do a "select FC_APPID"
to turn it on.

So honestly, it feels like

 (a) the "default y" is just completely wrong in all ways

 (b) this "config FC_APPID" shouldn't be a question AT ALL

IOW, it should likely purely be enabled by that 'select' for people
who decide they want BLK_CGROUP_FC_APPID (which properly defaults to

Pls advise. Or just send me a patch to fix it. Because the current
situation is most definitely not ok.


  parent reply	other threads:[~2021-07-02 22:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  8:11 [GIT PULL] first round of SCSI updates for the 5.13+ merge window James Bottomley
2021-07-02 22:37 ` pr-tracker-bot
2021-07-02 22:46 ` Linus Torvalds [this message]
2021-07-06 13:59 ` Marco Elver
2021-07-06 14:27   ` Martin K. Petersen
2021-07-06 14:34     ` Marco Elver
2021-07-06 14:40   ` Dan Carpenter

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='' \ \ \ \ \ \

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