[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200519034215.zr3gvrsokstxh2bs@vireshk-i7>
Date: Tue, 19 May 2020 09:12:15 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Bjorn Andersson <bjorn.andersson@...aro.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Georgi Djakov <georgi.djakov@...aro.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Linux PM list <linux-pm@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
Matthias Kaehlcke <mka@...omium.org>
Subject: Re: [PATCH] interconnect: Disallow interconnect core to be built as
a module
On 18-05-20, 20:37, Bjorn Andersson wrote:
> On Mon 18 May 20:31 PDT 2020, Viresh Kumar wrote:
>
> > On 18-05-20, 11:40, Bjorn Andersson wrote:
> > > It most certainly does.
> > >
> > > With INTERCONNECT as a bool we can handle its absence with stub
> > > functions - like every other framework does. But as a tristate then
> > > every driver with a call to the interconnect api needs an entry in
> > > Kconfig to ensure the client driver must be a module if the interconnect
> > > framework is.
> >
> > This patch has been pushed to linux-next a few days back.
> >
>
> Thanks Viresh, I had missed that.
Not your fault, we didn't resend it but simply applied the old version
itself :)
--
viresh
Powered by blists - more mailing lists