linux-kernel - Re: [PATCH] pinctrl: at91: use own header

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMAWPa_RuU73bPkxOwiqYjW3nH1DSCX+fOQ12T63SLiOVEBnyw@mail.gmail.com>
Date:	Wed, 29 Oct 2014 10:17:56 -0700
From:	Kevin Hilman <khilman@...nel.org>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	Nicolas Ferre <nicolas.ferre@...el.com>,
	Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Olof Johansson <olof@...om.net>
Subject: Re: [PATCH] pinctrl: at91: use own header

On Tue, Oct 28, 2014 at 9:17 AM, Linus Walleij <linus.walleij@...aro.org> wrote:
> On Fri, Oct 17, 2014 at 11:49 AM, Alexandre Belloni
> <alexandre.belloni@...e-electrons.com> wrote:
>
>> Copy the mach/at91_pio.h header locally and use it for pinctrl-at91.c. This
>> allows to remove the dependency on mach/at91_pio.h to be able to move at91 to
>> multiplatform.
>>
>> Signed-off-by: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
>
> Patch applied to the pinctrl tree with Nicolas' ACK.

This patch broke the build for sama5_defconfig in next-20141029[1], as
well as the other at91*defconfigs.

Kevin

[1] http://images.armcloud.us/kernel-ci//next/next-20141029/arm-sama5_defconfig/build.log
--
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/