[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170726091830.GI4039@linux-x5ow.site>
Date: Wed, 26 Jul 2017 11:18:30 +0200
From: Johannes Thumshirn <jthumshirn@...e.de>
To: Arnd Bergmann <arnd@...db.de>
Cc: "James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
"# 3.4.x" <stable@...r.kernel.org>, Hannes Reinecke <hare@...e.de>,
Finn Thain <fthain@...egraphics.com.au>,
James Smart <jsmart2021@...il.com>,
linux-scsi <linux-scsi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH, RESEND] scsi: lpfc: fix linking against modular NVMe
support
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@...e.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
Powered by blists - more mailing lists