From: Robin Murphy <robin.murphy@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kconfig: Remove last trace of GENERIC_IO
Date: Wed, 7 Feb 2018 17:26:56 +0000 [thread overview]
Message-ID: <dc837b10-a41d-4eb3-c14e-ca3fc69a55a9@arm.com> (raw)
In-Reply-To: <CAL_JsqJ1Hc8irF4LWM=1=OACC=fmRbg4c1evV777zKj3XOzi=w@mail.gmail.com>
On 07/02/18 17:15, Rob Herring wrote:
> On Feb 6, 2018 8:14 AM, "Robin Murphy" <robin.murphy@arm.com> wrote:
>>
>> On 06/02/18 16:06, Rob Herring wrote:
>>>
>>> On Tue, Feb 6, 2018 at 7:11 AM, Robin Murphy <robin.murphy@arm.com> wrote:
>>>>
>>>> Since commit 9de8da47742b ("kconfig: kill off GENERIC_IO option"), this
>>>> select has done nothing, and is now just confusing. Clean it up.
>>>>
>>>> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>>>> ---
>>>> lib/Kconfig | 1 -
>>>> 1 file changed, 1 deletion(-)
>>>
>>>
>>> We already have:
>>>
>>> https://lkml.org/lkml/2018/1/17/924
>>>
>>> and this series:
>>>
>>> https://lkml.org/lkml/2018/2/4/208
>>
>>
>> Agh, Ulf's patch is even sat in my inbox...
>>
>> This was just a drive-by from looking into HAS_IOMEM, sorry for the noise :)
>
> What are you looking into there? IMO, we should get rid of HAS_IOMEM.
> It's basically a !UML option to turn off a bunch of drivers in UML.
I was just having a quick investigate out of curiosity after Geert
raised it in the context of awkward COMPILE_TEST dependencies here:
https://lists.linuxfoundation.org/pipermail/iommu/2018-February/025963.html
I don't have the bandwidth myself to actually work on burying it, but it
does seem like that might be feasible.
Robin.
prev parent reply other threads:[~2018-02-07 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 13:11 Robin Murphy
2018-02-06 16:06 ` Rob Herring
2018-02-06 16:14 ` Robin Murphy
2018-02-07 17:15 ` Rob Herring
2018-02-07 17:26 ` Robin Murphy [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=dc837b10-a41d-4eb3-c14e-ca3fc69a55a9@arm.com \
--to=robin.murphy@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®