* akpm@xxxxxxxxxxxxxxxxxxxx <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > The patch titled > Allow rwlocks to re-enable interrupts > has been added to the -mm tree. Its filename is > allow-rwlocks-to-re-enable-interrupts.patch > > Before you just go and hit "reply", please: > a) Consider who else should be cc'ed > b) Prefer to cc a suitable mailing list as well > c) Ideally: find the original patch on the mailing list and do a > reply-to-all to that, adding suitable additional cc's > > *** Remember to use Documentation/SubmitChecklist when testing your code *** > > See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find > out what to do about this > > The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ > > ------------------------------------------------------ > Subject: Allow rwlocks to re-enable interrupts > From: Robin Holt <holt@xxxxxxx> > > Pass the original flags to rwlock arch-code, so that it can re-enable > interrupts if implemented for that architecture. > > Initially, make __raw_read_lock_flags and __raw_write_lock_flags stubs > which just do the same thing as non-flags variants. > > Signed-off-by: Petr Tesarik <ptesarik@xxxxxxx> > Signed-off-by: Robin Holt <holt@xxxxxxx> > Acked-by: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> > Cc: <linux-arch@xxxxxxxxxxxxxxx> > Cc: Ingo Molnar <mingo@xxxxxxx> Acked-by: Ingo Molnar <mingo@xxxxxxx> thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
