On Thu, Mar 29, 2012 at 06:21:23PM +0200, Jean Delvare wrote: > On Wed, 28 Mar 2012 15:38:08 -0700, [email protected] wrote: > > > > The patch below does not apply to the 3.3-stable tree. > > If someone wants it applied there, or to any other stable or longterm > > tree, then please email the backport, including the original git commit > > id to <[email protected]>. > > > > thanks, > > > > greg k-h > > > > ------------------ original commit in Linus's tree ------------------ > > > > From 855cc454341c6ca1212bf86939f2f2a51ab54e18 Mon Sep 17 00:00:00 2001 > > From: Jean Delvare <[email protected]> > > Date: Sat, 18 Feb 2012 17:54:23 +0100 > > Subject: [PATCH] mfd: Fix ACPI conflict check > > (...) > > Hmm, this is very strange. > > $ git name-rev 855cc454341c6ca1212bf86939f2f2a51ab54e18 > 855cc454341c6ca1212bf86939f2f2a51ab54e18 master~17^2~56 > > This would suggest that the fix was committed after v3.3, as this is > the last tag that was created by Linus. However this is not true, if > you download linux-3.3.tar.xz, you'll see the fix is present in this > version already. > > Also, the fix has already been backported to 3.2 and 3.0 stable kernel > series (in 3.2.10 and 3.0.24, respectively) so there is no reason to do > that again. > > I have no idea how this is possible at all, sorry.
Ah, it looks like it went in as commit 81b5482c32769abb6dfb979560dab2f952ba86fa which showed up in 3.3-rc7, and then came in again through some other tree after 3.3 was out, and I saw that one now. No worries, this happens at times. thanks for looking into it. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
