linux-kernel - Re: spi/bcm63xx: unknown CONFIG_BIG

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]

Date:	Tue, 15 Sep 2015 15:34:17 +0200
From:	Jonas Gorski <jogo@...nwrt.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	Valentin Rothberg <valentinrothberg@...il.com>,
	Paul Bolle <pebolle@...cali.nl>, ziegler@...fau.de,
	linux-kernel@...r.kernel.org
Subject: Re: spi/bcm63xx: unknown CONFIG_BIG_ENDIAN

On 15.09.2015 10:40, Mark Brown wrote:
> On Tue, Sep 15, 2015 at 09:40:30AM +0200, Jonas Gorski wrote:
> 
>> Mark? If you can drop patches 2 to 4 that would be easiest for me, but if
>> you don't do rebases on your for-next branch, then I'll rewrite the
>> patches to apply on top of the already applied old versions and send a v3.
> 
> No, please submit incremental modifications as incremental
> modifications.

IS there anything I can do to avoid this happining again, like a patchwork
where I can mark my older versions as superseded? I admit I didn't expect
partial application of the (old) series.


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