linux-kernel - Re: linux-next: manual merge of the msm tree with the arm 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: <1287516263.10071.54.camel@c-dwalke-linux.qualcomm.com>
Date:	Tue, 19 Oct 2010 12:24:23 -0700
From:	Daniel Walker <dwalker@...o99.com>
To:	Russell King <rmk@....linux.org.uk>
Cc:	Nicolas Pitre <nico@...xnic.net>, Arnd Bergmann <arnd@...db.de>,
	Joe Perches <joe@...ches.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
	Jeremy Kerr <jeremy.kerr@...onical.com>,
	Jeff Ohlstein <johlstei@...eaurora.org>
Subject: Re: linux-next: manual merge of the msm tree with the arm tree

On Tue, 2010-10-19 at 19:53 +0100, Russell King wrote:
> On Tue, Oct 19, 2010 at 11:42:37AM -0700, Daniel Walker wrote:
> > 
> > > That's why on occasions we do transgress the established process to 
> > > accommodate such changes.  Imagine just for a moment the patch that 
> > > modified the interrupt callback prototype to remove the useless pt_regs 
> > > argument.  Obviously, it had to be done atomically to the _whole_ tree, 
> > > and it was agreed that this patch was to be applied at the end of the 
> > > merge window.  But no one expected a single minute sending a CC to _all_ 
> > > the driver authors.
> > 
> > I don't actually know which patch your talking about, but it sounds
> > pretty simple.. I'm not really addressing really simple fixes, even tho
> > changing a single parameter on a function could be done broken up
> > depending on what it is.
> 
> As you think that it's a simple matter, I challenge you to break this
> change up in a way that doesn't result in any build breakage:
> 	7d12e780e003f93433d49ce78cfedf4b4c52adc5

I wasn't saying it's simple to break patches up. I was just saying the
patch sounded like something simple, like running sed over the source or
a change replace type patch.

I'll look at the patch you reference tho, maybe I can break it up.

Daniel

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