From: Johannes Thumshirn <jthumshirn@suse.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"# 3.4.x" <stable@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>,
Finn Thain <fthain@telegraphics.com.au>,
James Smart <jsmart2021@gmail.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH, RESEND] scsi: lpfc: fix linking against modular NVMe support
Date: Wed, 26 Jul 2017 11:18:30 +0200 [thread overview]
Message-ID: <20170726091830.GI4039@linux-x5ow.site> (raw)
In-Reply-To: <CAK8P3a2EnPuTNU0O5va+Xz3nCthhpz3Po1z7SOVRiAUV_2+OhA@mail.gmail.com>
On Wed, Jul 26, 2017 at 11:16:10AM +0200, Arnd Bergmann wrote:
> We use this construct in many places these days. A few years ago I added
> a comment whenever I added an instance, but most others don't so I treat
> it as an idiom now.
>
> "depends on X" means that if X=m, the current symbol can only be "m" or
> "n", while "X=y" means it can have any value.
>
> So for "depends on X || X=n", the current symbol cannot be "y" when "X=m",
> but otherwise can have any of the three possibilities. This is exactly what
> we need here.
Obvious o.O
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
prev parent reply other threads:[~2017-07-26 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 20:53 [PATCH, RESEND] scsi: lpfc: fix linking against modular NVMe support Arnd Bergmann
2017-07-26 9:08 ` Johannes Thumshirn
2017-07-26 9:16 ` Arnd Bergmann
2017-07-26 9:17 ` Arnd Bergmann
2017-07-26 9:19 ` Johannes Thumshirn
2017-07-26 9:18 ` Johannes Thumshirn [this message]
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=20170726091830.GI4039@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=arnd@arndb.de \
--cc=fthain@telegraphics.com.au \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jsmart2021@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).