public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: "linux-samsung-soc@vger.kernel.org" 
	<linux-samsung-soc@vger.kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Gwendal Grignou <gwendal@google.com>,
	Doug Anderson <dianders@chromium.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 0/3] mfd: ChromeOS EC Kconfig dependency cleanup
Date: Mon, 10 Aug 2015 17:13:01 +0100	[thread overview]
Message-ID: <20150810161301.GA13253@x1> (raw)
In-Reply-To: <20150810161009.GG12631@x1>

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@collabora.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

  reply	other threads:[~2015-08-10 16:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  0:20 [PATCH 0/3] mfd: ChromeOS EC Kconfig dependency cleanup Javier Martinez Canillas
2015-06-25  0:20 ` [PATCH 1/3] platform/chrome: Don't make CHROME_PLATFORMS depends on X86 || ARM Javier Martinez Canillas
2015-07-22  1:29   ` Olof Johansson
2015-07-22  7:16   ` Lee Jones
2015-08-17  7:56   ` Geert Uytterhoeven
2015-08-17  8:36     ` Javier Martinez Canillas
2015-06-25  0:20 ` [PATCH 2/3] mfd: Remove MFD_CROS_EC " Javier Martinez Canillas
2015-06-25  8:38   ` Lee Jones
2015-06-25  8:44     ` Javier Martinez Canillas
2015-06-30  6:09       ` Paul Gortmaker
2015-07-22  1:13       ` Paul Gortmaker
2015-07-22  1:27         ` Javier Martinez Canillas
2015-07-22  1:31         ` Olof Johansson
2015-07-22  1:30       ` Olof Johansson
2015-07-22  7:15     ` Lee Jones
2015-06-25  0:20 ` [PATCH 3/3] mfd: Remove MFD_CROS_EC_SPI depends on OF Javier Martinez Canillas
2015-06-25  8:38   ` Lee Jones
2015-07-22  7:17     ` Lee Jones
2015-08-07  0:03 ` [PATCH 0/3] mfd: ChromeOS EC Kconfig dependency cleanup Javier Martinez Canillas
2015-08-10 16:10   ` Lee Jones
2015-08-10 16:13     ` Lee Jones [this message]
2015-08-10 16:45       ` Javier Martinez Canillas

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=20150810161301.GA13253@x1 \
    --to=lee.jones@linaro.org \
    --cc=dianders@chromium.org \
    --cc=gwendal@google.com \
    --cc=heiko@sntech.de \
    --cc=javier@dowhile0.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=paul.gortmaker@windriver.com \
    --cc=sameo@linux.intel.com \
    /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