From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
"kbuild-all@01.org" <kbuild-all@01.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [renesas:drivers-for-v4.13 3/3] drivers/soc/renesas/rcar-sysc.c:209:19: error: 'GENPD_FLAG_ALWAYS_ON' undeclared
Date: Thu, 15 Jun 2017 20:52:31 +0200 [thread overview]
Message-ID: <20170615185226.GA9808@verge.net.au> (raw)
In-Reply-To: <CAMuHMdXU-VPi-kVPjSXT2VdAc53DkGzqbWerUjparSyH+B10fQ@mail.gmail.com>
On Thu, Jun 15, 2017 at 04:31:48PM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Thu, Jun 15, 2017 at 4:20 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Thu, Jun 15, 2017 at 04:08:56PM +0200, Geert Uytterhoeven wrote:
> >> On Thu, Jun 15, 2017 at 3:45 PM, Simon Horman <horms@verge.net.au> wrote:
> >> depends on commit ffaa42e8a40b7f10 ("PM / Domains: Enable users of genpd
> >> to specify always on PM domains") in v4.12-rc1.
> >>
> >> It does not depend on anything else that's only in fixes-for-v4.12.
> >
> > Ok, that is clear. But for some reason I thought that
> >
> > "soc: renesas: Rework Kconfig and Makefile logic" depends on
> > "soc: renesas: Provide dummy rcar_rst_read_mode_pins() for compile-testing"
>
> Yes, it does, as the former reworks the dummy provided by the latter.
>
> But "soc: renesas: rcar-sysc: Use GENPD_FLAG_ALWAYS_ON" does not depend
> on any of these.
>
> But now I understand the issue you're facing: drivers-for-v4.13 depends both on
> commits in v4.12-rc1, and on fixes still destined for v4.12.
Yes, that is the one.
I think the simplest solution is to base drivers-for-v4.13 on a merge of
v4.12-rc1 and fixes-for-v4.13.
next prev parent reply other threads:[~2017-06-15 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 11:04 [renesas:drivers-for-v4.13 3/3] drivers/soc/renesas/rcar-sysc.c:209:19: error: 'GENPD_FLAG_ALWAYS_ON' undeclared kbuild test robot
2017-06-14 11:31 ` Geert Uytterhoeven
2017-06-15 13:45 ` Simon Horman
2017-06-15 14:08 ` Geert Uytterhoeven
2017-06-15 14:20 ` Simon Horman
2017-06-15 14:31 ` Geert Uytterhoeven
2017-06-15 18:52 ` Simon Horman [this message]
2017-06-15 19:15 ` Simon Horman
2017-06-16 7:05 ` Geert Uytterhoeven
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=20170615185226.GA9808@verge.net.au \
--to=horms@verge.net.au \
--cc=fengguang.wu@intel.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=kbuild-all@01.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.