linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: linux-next: build failure after merge of the final tree (gpio tree related)
Date: Tue, 29 Oct 2013 14:28:34 +0100	[thread overview]
Message-ID: <CACRpkdb_n+bDq3hMR++r2Xr_sWnDVek492XeHAMh5Jtd53-woA@mail.gmail.com> (raw)
In-Reply-To: <20131029011223.58b51e529acced32d6dae82a@canb.auug.org.au>

On Mon, Oct 28, 2013 at 3:12 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Caused by commit 79a9becda894 ("gpiolib: export descriptor-based GPIO
> interface") from the gpio tree.
>
> I have applied this fix up patch for today:
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 29 Oct 2013 01:06:23 +1100
> Subject: [PATCH] gpiolib: provide a declaration of seq_file in gpio/driver.h
>
> Fixes this build error:
>
> In file included from include/asm-generic/gpio.h:13:0,
>                  from include/linux/gpio.h:51,
>                  from include/linux/of_gpio.h:20,
>                  from arch/powerpc/sysdev/ppc4xx_gpio.c:29:
> include/linux/gpio/driver.h:85:14: error: 'struct seq_file' declared inside parameter list [-Werror]
> include/linux/gpio/driver.h:85:14: error: its scope is only this definition or declaration, which is probably not what you want [-Werror]
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>

Patch applied to the GPIO tree, thanks for fixing up our mess!

Yours,
Linus Walleij

  reply	other threads:[~2013-10-29 13:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 14:12 linux-next: build failure after merge of the final tree (gpio tree related) Stephen Rothwell
2013-10-29 13:28 ` Linus Walleij [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-05  6:35 Stephen Rothwell
2014-03-05  7:16 ` Linus Walleij
2014-03-05 16:42   ` Fabian Vogt
2013-12-23  4:54 Stephen Rothwell
2013-10-29  9:10 Stephen Rothwell
2013-10-29 13:25 ` Linus Walleij
2013-10-30  0:56   ` Alex Courbot
2012-02-06  4:23 Stephen Rothwell
2012-02-06  6:07 ` Grant Likely
2012-02-06 14:02   ` Mark Brown

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=CACRpkdb_n+bDq3hMR++r2Xr_sWnDVek492XeHAMh5Jtd53-woA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=acourbot@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).