All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:45:42 +0200	[thread overview]
Message-ID: <20170615134541.GA22158@verge.net.au> (raw)
In-Reply-To: <CAMuHMdUkhpGGJPNLKmWn1znNcLFL7e7nqp6QK59qCd0Y8i22-w@mail.gmail.com>

On Wed, Jun 14, 2017 at 01:31:41PM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
> 
> On Wed, Jun 14, 2017 at 1:04 PM, kbuild test robot
> <fengguang.wu@intel.com> wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git drivers-for-v4.13
> > head:   895c7e91d84c0f0e207ad909482ed70b5f3c806f
> > commit: 895c7e91d84c0f0e207ad909482ed70b5f3c806f [3/3] soc: renesas: rcar-sysc: Use GENPD_FLAG_ALWAYS_ON
> > config: ia64-allmodconfig (attached as .config)
> > compiler: ia64-linux-gcc (GCC) 6.2.0
> > reproduce:
> >         wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> >         chmod +x ~/bin/make.cross
> >         git checkout 895c7e91d84c0f0e207ad909482ed70b5f3c806f
> >         # save the attached .config to linux build tree
> >         make.cross ARCH=ia64
> >
> > All errors (new ones prefixed by >>):
> >
> >    drivers/soc/renesas/rcar-sysc.c: In function 'rcar_sysc_pd_setup':
> >>> drivers/soc/renesas/rcar-sysc.c:209:19: error: 'GENPD_FLAG_ALWAYS_ON' undeclared (first use in this function)
> >       genpd->flags |= GENPD_FLAG_ALWAYS_ON;
> 
> Looks like your drivers-for-v4.13 is based on v4.11-rc1
> (renesas-fixes-for-v4.12) instead of v4.12-rc1.
> Can you please rebase it?

It is based on renesas-fixes-for-v4.12 because I was under the impression
that the patch there is a dependency for (other) patches in renesas drivers.
Is that the case? If so I think the correct (new) base would be v4.12-rc2.

> Thanks!
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds
> 

  reply	other threads:[~2017-06-15 13:45 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 [this message]
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
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=20170615134541.GA22158@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.