From: Paul Gortmaker <paul.gortmaker@windriver•com>
To: Javier Martinez Canillas <javier.martinez@collabora•co.uk>
Cc: Lee Jones <lee.jones@linaro•org>,
linux-samsung-soc@vger•kernel.org,
Heiko Stuebner <heiko@sntech•de>,
Gwendal Grignou <gwendal@google•com>,
Doug Anderson <dianders@chromium•org>,
linux-kernel@vger•kernel.org,
Samuel Ortiz <sameo@linux•intel.com>,
linux-next@vger•kernel.org, sparclinux@vger•kernel.org,
Olof Johansson <olof@lixom•net>
Subject: Re: [PATCH 2/3] mfd: Remove MFD_CROS_EC depends on X86 || ARM
Date: Tue, 21 Jul 2015 21:13:00 -0400 [thread overview]
Message-ID: <20150722011300.GF4477@windriver.com> (raw)
In-Reply-To: <558BBF6C.7000906@collabora.co.uk>
[Re: [PATCH 2/3] mfd: Remove MFD_CROS_EC depends on X86 || ARM] On 25/06/2015 (Thu 10:44) Javier Martinez Canillas wrote:
> Hello Lee,
>
> On 06/25/2015 10:38 AM, Lee Jones wrote:
> > On Thu, 25 Jun 2015, Javier Martinez Canillas wrote:
> >
> >> A dependency on X86 || ARM for MFD_CROS_EC was added to fix the warning:
> >>
> >> (MFD_CROS_EC) selects CHROME_PLATFORMS which has unmet direct dependencies (X86 || ARM)
> >>
> >> This happened because CHROME_PLATFORMS had a dependency on X86 || ARM but
> >> that dependency was removed since there isn't a reason why the option can
> >> not be selected on other architectures. So now the above warning will not
> >> happen and the MFD_CROS_EC dependency can be removed since is not needed.
> >>
> >> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora•co.uk>
> >> ---
> >>
> >> drivers/mfd/Kconfig | 1 -
> >> 1 file changed, 1 deletion(-)
> >
> > Applied for v4.3, thanks.
> >
>
> Thanks a lot.
>
> Olof,
>
> Could you please ack patch 1/3 so Lee can pick it through the mfd tree?
> Since both patches 1/3 and 2/3 are needed to fix the build warning for
> !X86 and !ARM architectures.
Hi all,
Wondering if this fell through the cracks. It used to be just a
linux-next issue, but now it is a mainline issue. This _really_ should
be fixed and fed to Linus ASAP. Ideally it should have been fixed before
going to mainline as it was reported in plenty of time ; that is the
whole point of linux-next.... to fix unanticipated fallout and revise.
------------------
paul@builder:~/git/linux-head$ git describe
v4.2-rc3
paul@builder:~/git/linux-head$ echo $ARCH
sparc64
paul@builder:~/git/linux-head$ make allyesconfig
scripts/kconfig/conf --allyesconfig Kconfig
warning: (MFD_CROS_EC) selects CHROME_PLATFORMS which has unmet direct dependencies (X86 || ARM)
#
# configuration written to .config
#
paul@builder:~/git/linux-head$
------------------
Thanks,
Paul.
--
>
> Best regards,
> Javier
next parent reply other threads:[~2015-07-22 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1435191645-6022-1-git-send-email-javier.martinez@collabora.co.uk>
[not found] ` <1435191645-6022-3-git-send-email-javier.martinez@collabora.co.uk>
[not found] ` <20150625083854.GV15013@x1>
[not found] ` <558BBF6C.7000906@collabora.co.uk>
2015-07-22 1:13 ` Paul Gortmaker [this message]
2015-07-22 1:27 ` [PATCH 2/3] mfd: Remove MFD_CROS_EC depends on X86 || ARM Javier Martinez Canillas
2015-07-22 1:31 ` Olof Johansson
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=20150722011300.GF4477@windriver.com \
--to=paul.gortmaker@windriver$(echo .)com \
--cc=dianders@chromium$(echo .)org \
--cc=gwendal@google$(echo .)com \
--cc=heiko@sntech$(echo .)de \
--cc=javier.martinez@collabora$(echo .)co.uk \
--cc=lee.jones@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-samsung-soc@vger$(echo .)kernel.org \
--cc=olof@lixom$(echo .)net \
--cc=sameo@linux$(echo .)intel.com \
--cc=sparclinux@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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