[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFkk2KScFZE0sjZovi1vq2xBQ_-wx2XoSbWG6_qL2W0rR5B7YQ@mail.gmail.com>
Date: Fri, 23 Feb 2018 00:42:28 +0100
From: Ulf Magnusson <ulfalizer@...il.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Tomasz Figa <tfiga@...omium.org>,
Paul Burton <paul.burton@...s.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Hans-Christian Noren Egtvedt <egtvedt@...fundet.no>,
Linus Walleij <linus.walleij@...aro.org>,
Vineet Gupta <vgupta@...opsys.com>,
Mel Gorman <mgorman@...hsingularity.net>,
Christoph Hellwig <hch@....de>,
Michal Nazarewicz <mina86@...a86.com>,
Rob Herring <robh@...nel.org>,
Stephen Boyd <sboyd@...eaurora.org>,
Paul Mackerras <paulus@...abs.org>,
Will Deacon <will.deacon@....com>,
Tony Lindgren <tony@...mide.com>,
Nicholas Piggin <npiggin@...il.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org
Subject: Re: [PATCH v2 20/20] x86/PCI: VMD: Fix malformed Kconfig default
On Fri, Feb 23, 2018 at 12:00 AM, Bjorn Helgaas <helgaas@...nel.org> wrote:
> On Tue, Feb 06, 2018 at 11:11:06PM +0100, Ulf Magnusson wrote:
>> 'default N' should be 'default n', though they happen to have the same
>> effect here, due to undefined symbols (N in this case) evaluating to n
>> in a tristate sense.
>>
>> Remove the default instead of changing it. bool and tristate symbols
>> implicitly default to n.
>
> s/bool/Bool/
Not a great excuse, but I was thinking syntactically -- 'bool' and
'tristate' symbols... :)
>
>> Discovered with the
>> https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py
>> script.
>>
>> Signed-off-by: Ulf Magnusson <ulfalizer@...il.com>
>
> Acked-by: Bjorn Helgaas <bhelgaas@...gle.com>
>
> Since only this patch was posted to linux-pci, I assume it will be merged
> via some other tree.
I didn't have a particular tree in mind for this patchset. I imagined
people would pick up patches into the trees where they make the most
sense, and only created the patchset to keep track of the patches more
easily. Might have created some confusion in retrospect.
I just did a --cc-cmd="scripts/get_maintainer.pl -i" for the
individual patches by the way.
Cheers,
Ulf
Powered by blists - more mailing lists