[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150810161301.GA13253@x1>
Date: Mon, 10 Aug 2015 17:13:01 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Javier Martinez Canillas <javier@...hile0.org>
Cc: "linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
Heiko Stuebner <heiko@...ech.de>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Gwendal Grignou <gwendal@...gle.com>,
Doug Anderson <dianders@...omium.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
Olof Johansson <olof@...om.net>
Subject: Re: [PATCH 0/3] mfd: ChromeOS EC Kconfig dependency cleanup
On Mon, 10 Aug 2015, Lee Jones wrote:
> On Fri, 07 Aug 2015, Javier Martinez Canillas wrote:
> > On Thu, Jun 25, 2015 at 2:20 AM, Javier Martinez Canillas
> > <javier.martinez@...labora.co.uk> wrote:
> > >
> > > This is a trivial series that do some changes to the dependency for the
> > > ChromeOS EC drivers Kconfig symbols. The patches are on top of Paul's
> > > patch "mfd: fix dependency warning for CHROME_PLATFORMS on !X86, !ARM":
> > > https://lkml.org/lkml/2015/6/20/219.
> > >
> > > Paul fixed a warning about unmet dependencies but I think the correct fix
> > > is to remove unneded dependencies. So that is what this series do and are
> > > composed of the following patches:
> > >
> > >
> > > Javier Martinez Canillas (3):
> > > platform/chrome: Don't make CHROME_PLATFORMS depends on X86 || ARM
> > > mfd: Remove MFD_CROS_EC depends on X86 || ARM
> > > mfd: Remove MFD_CROS_EC_SPI depends on OF
> > >
> > > drivers/mfd/Kconfig | 3 +--
> > > drivers/platform/chrome/Kconfig | 1 -
> > > 2 files changed, 1 insertion(+), 3 deletions(-)
> > >
> >
> > The warning that this series fixes has appeared again in linux-next.
> > You said some time ago that applied the patches for 4.3 [0] and indeed
> > I remember the warning going away at some point.
> >
> > Do you know what happened with this patches? I see 3/3 in linux-next
> > but no 1/3 and 2/3.
>
> No idea why you're not seeing them. They are in my -fixes branch,
> which is pulled into -next. I have _just_ sent them to Linus for
> inclusion into v4.2.
Okay, scrap that. It likes like MFD -fixes isn't pulled into -next.
I'll see what I can do about that.
> Let me know if you still see the issue.
>
> > [0]: https://lkml.org/lkml/2015/6/25/115
> >
> > Thanks a lot and best regards,
> > Javier
>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists