linux-kernel - Re: [PATCH 3/5] x86: coding style fixes in arch/x86/ia32/ia32

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, 08 Jan 2008 23:55:09 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Sam Ravnborg <sam@...nborg.org>
CC:	Ingo Molnar <mingo@...e.hu>, Rik van Riel <riel@...hat.com>,
	Paolo Ciarrocchi <paolo.ciarrocchi@...il.com>,
	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	Linux Kernel <linux-kernel@...r.kernel.org>, trivial@...nel.org
Subject: Re: [PATCH 3/5] x86: coding style fixes in arch/x86/ia32/ia32_aout.c

On 01/08/2008 11:17 PM, Sam Ravnborg wrote:
>>> Most of these kernel changes would probably get in the way of real 
>>> development, making patches reject that would otherwise apply.
>> I'm curious, in what way would they interfere?
> 
> Developer A work one some complicated stuff in foo.c which is
> not yet -mm fooder.
> 
> Developer B submits and have applied a massive cleanup to some of the
> files touced by Developer A's patch.
> 
> Developer A now needs to fix up his stuff.

Ok, to be honest, how often is this a problem?

And then, how hard is it to rebase the patch?

And if it is a problem, then you can still drop a message, such as don't do 
this, I have a big patch here.
--
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/