linux-kernel - Re: linux-next: build failure after merge of the gpio tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150513073613.GA1907@localhost>
Date:	Wed, 13 May 2015 09:36:13 +0200
From:	Johan Hovold <johan@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Johan Hovold <johan@...nel.org>,
	Alexandre Courbot <acourbot@...dia.com>
Subject: Re: linux-next: build failure after merge of the gpio tree

On Wed, May 13, 2015 at 04:55:16PM +1000, Stephen Rothwell wrote:
> Hi Linus,
> 
> After merging the gpio tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/gpio/gpio-dln2.c: In function 'dln2_gpio_probe':
> drivers/gpio/gpio-dln2.c:469:12: error: 'struct gpio_chip' has no member named 'exported'
>   dln2->gpio.exported = true;
>             ^
> 
> Caused by commit 6a4b6b0a3b55 ("gpio: sysfs: clean up chip class-device
> handling").
> 
> I have used the gpio tree from next-20150512 for today.

A fix for this was posted yesterday (when detected by the kbuild test
robot):

	https://lkml.org/lkml/2015/5/12/437

Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/