On Mon, Oct 22, 2012 at 05:57:38PM -0400, David Miller wrote: > > Please queue up the following fixes for 3.0, 3.2, 3.4, and > 3.6 -stable branches, respectively.
These mboxes are not all "sequential". For example, the 3.4 set of patches contained 5 patches: 1 N Oct 10 Al Viro ( 79) [PATCH 1/6] sparc64: fix ptrace interaction with force_successful_syscall_return() 2 N Oct 14 David S. Miller ( 47) [PATCH 2/6] sparc64: Like x86 we should check current->mm during perf backtrace generation. 3 N Oct 16 David S. Miller ( 45) [PATCH 4/6] sparc64: Fix bit twiddling in sparc_pmu_enable_event(). 4 N Aug 01 Jiri Kosina ( 47) [PATCH 5/6] sparc64: do not clobber personality flags in sys_sparc64_personality() 5 N Aug 15 David S. Miller ( 71) [PATCH 6/6] sparc64: Be less verbose during vmemmap population. Yet the description says there is 6? Same for the 3.6 mbox: 1 N Oct 10 Al Viro ( 79) [PATCH 1/4] sparc64: fix ptrace interaction with force_successful_syscall_return() 2 N Oct 14 David S. Miller ( 47) [PATCH 2/4] sparc64: Like x86 we should check current->mm during perf backtrace generation. 3 N Oct 16 David S. Miller ( 44) [PATCH 4/4] sparc64: Fix bit twiddling in sparc_pmu_enable_event(). Only 3 patches, yet the sequence says there is 4? The 3.0 mbox also is confused: 1 N Oct 10 Al Viro ( 79) [PATCH 1/6] sparc64: fix ptrace interaction with force_successful_syscall_return() 2 N Oct 14 David S. Miller ( 47) [PATCH 2/6] sparc64: Like x86 we should check current->mm during perf backtrace generation. 3 N Oct 16 David S. Miller ( 45) [PATCH 4/6] sparc64: Fix bit twiddling in sparc_pmu_enable_event(). 4 N Aug 01 Jiri Kosina ( 47) [PATCH 5/6] sparc64: do not clobber personality flags in sys_sparc64_personality() 5 N Aug 15 David S. Miller ( 71) [PATCH 6/6] sparc64: Be less verbose during vmemmap population. I didn't look at the 3.2 mbox. Did I get something wrong here? Should there really be a missing patch from each of these? Just want to verify before I apply anything. thanks, 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
