[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87df1eda7d8e28f49a92def8bfe4d549494d2db0.camel@linux.ibm.com>
Date: Wed, 18 May 2022 15:47:17 +0200
From: Niklas Schnelle <schnelle@...ux.ibm.com>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
linux-pci@...r.kernel.org, Arnd Bergmann <arnd@...nel.org>,
Alessandro Zummo <a.zummo@...ertech.it>,
"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
<linux-rtc@...r.kernel.org>
Subject: Re: [RFC v2 29/39] rtc: add HAS_IOPORT dependencies
On Wed, 2022-05-18 at 00:15 +0200, Alexandre Belloni wrote:
> Hi,
>
> On 29/04/2022 15:50:49+0200, Niklas Schnelle wrote:
> > In a future patch HAS_IOPORT=n will result in inb()/outb() and friends
> > not being declared. We thus need to add HAS_IOPORT as dependency for
> > those drivers using them.
> >
>
> I'm fine taking that this cycle if there are no dependencies. Should I?
>
I'd say the dependency here is the first patch in the series and we
don't seem to have full consensus on this yet. So as of now I sadly
don't think so.
Powered by blists - more mailing lists