[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VecYSVwFii3MCYSs0VyTF=d_mF1cbu4samLKN6=i2L13A@mail.gmail.com>
Date: Tue, 27 Feb 2018 17:47:31 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Jan Kiszka <jan.kiszka@...mens.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H . Peter Anvin" <hpa@...or.com>,
Bjorn Helgaas <bhelgaas@...gle.com>, x86@...nel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
jailhouse-dev@...glegroups.com, linux-pci@...r.kernel.org,
virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH 4/6] x86: Consolidate PCI_MMCONFIG configs
On Tue, Feb 27, 2018 at 9:19 AM, Jan Kiszka <jan.kiszka@...mens.com> wrote:
> On 2018-01-28 18:26, Andy Shevchenko wrote:
>> On Mon, Jan 22, 2018 at 8:12 AM, Jan Kiszka <jan.kiszka@...mens.com> wrote:
>>> From: Jan Kiszka <jan.kiszka@...mens.com>
>>>
>>> Not sure if those two worked by design or just by chance so far. In any
>>> case, it's at least cleaner and clearer to express this in a single
>>> config statement.
>>
>> Congrats! You found by the way a bug in
>>
>> commit e279b6c1d329e50b766bce96aacc197eae8a053b
>> Author: Sam Ravnborg <sam@...nborg.org>
>> Date: Tue Nov 6 20:41:05 2007 +0100
>>
>> x86: start unification of arch/x86/Kconfig.*
>>
>> ...and proper fix seems to split PCI stuff to common + X86_32 only + X86_64 only
>>
>
> Hmm, is that a change request on this patch?
>From my side it's a suggestion.
Better wait for the answer from x86 maintainers.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists