All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: Re: Build failures in v4.9-stable-queue (drivers/pinctrl/sh-pfc/pfc-r8a7795.c)
Date: Wed, 18 Jan 2017 08:04:49 +0100	[thread overview]
Message-ID: <20170118070449.GA28812@kroah.com> (raw)
In-Reply-To: <20170118070348.GA11886@kroah.com>

On Wed, Jan 18, 2017 at 08:03:48AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Jan 17, 2017 at 09:22:38PM -0800, Guenter Roeck wrote:
> > drivers/pinctrl/sh-pfc/pfc-r8a7795.c:5191:38: error: array type has incomplete element type ‘struct sh_pfc_bias_info’
> >  static const struct sh_pfc_bias_info bias_info[] = {
> >                                       ^
> > drivers/pinctrl/sh-pfc/pfc-r8a7795.c: In function ‘r8a7795_pinmux_get_bias’:
> > drivers/pinctrl/sh-pfc/pfc-r8a7795.c:5362:9: error: implicit declaration of function ‘sh_pfc_pin_to_bias_info’ [-Werror=implicit-function-declaration]
> >   info = sh_pfc_pin_to_bias_info(bias_info, ARRAY_SIZE(bias_info), pin);
> > 
> > This affects arm64 builds (defconfig, allmodconfig).
> > 
> > Guess something is missing in commit 30c49bf7c504 ("pinctrl: sh-pfc: r8a7795:
> > Use lookup function for bias data"). Copying the author.
> 
> Looks like I need to add c314c9f15aa5 ("pinctrl: sh-pfc: Add helper to
> handle bias lookup table") to handle this.
> 
> Odd that kbuild didn't find this issue, your build system covers more
> than it does :)

I take it back, I now see the kbuild failure message as well.

greg k-h

  reply	other threads:[~2017-01-18  7:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  5:22 Build failures in v4.9-stable-queue (drivers/pinctrl/sh-pfc/pfc-r8a7795.c) Guenter Roeck
2017-01-18  7:03 ` Greg Kroah-Hartman
2017-01-18  7:04   ` Greg Kroah-Hartman [this message]
2017-01-18  7:36   ` Niklas Söderlund
2017-01-18  7:47     ` Greg Kroah-Hartman

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=20170118070449.GA28812@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux@roeck-us.net \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=stable@vger.kernel.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.