linux-kernel - Re: [RFC 17/17] unicore32: default GENERIC

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

Message-Id: <201303121210.29613.arnd@arndb.de>
Date:	Tue, 12 Mar 2013 12:10:29 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Alexandre Courbot <gnurou@...il.com>
Cc:	Ralf Baechle <ralf@...ux-mips.org>,
	Chris Zankel <chris@...kel.net>,
	Guan Xuetao <gxt@...c.pku.edu.cn>,
	Kumar Gala <galak@...nel.crashing.org>, acourbot@...dia.com,
	Jonas Bonn <jonas@...thpole.se>,
	Haavard Skinnemoen <hskinnemoen@...il.com>,
	Vitaly Bordug <vitb@...nel.crashing.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Josh Boyer <jwboyer@...il.com>,
	"Hans-Christian Egtvedt" <egtvedt@...fundet.no>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Mike Frysinger <vapier@...too.org>,
	Paul Mundt <lethal@...ux-sh.org>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Matt Porter <mporter@...nel.crashing.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Marcelo Tosatti <marcelo@...ck.org>,
	Paul Mackerras <paulus@...ba.org>,
	Max Filippov <jcmvbkbc@...il.com>,
	Russell King <linux@....linux.org.uk>
Subject: Re: [RFC 17/17] unicore32: default GENERIC_GPIO to false

On Tuesday 12 March 2013, Alexandre Courbot wrote:
> Thanks, I will fix this in the next version.
> 
> Btw, if this (or rather the next iteration) gets merged, may I suggest to
> do it through the GPIO tree instead of having each architecture picking the
> patches of relevance. A considerable number of other patches that depend on
> this will follow and this will ensure they are picked in the right order.

Sounds reasonable, but I would also suggest you prepare a branch that can
get merged into the GPIO, ARM, PowerPC and MIPS trees to avoid merge
conflicts in that case, since these all will have a number of changes
conflicting with yours.

In the end, I would not care which tree it gets merged through, as long
as all have the same version of your patches.

	Arnd
--
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/