From: tom.leiming@gmail.com (Ming Lei)
To: linux-arm-kernel@lists.infradead.org
Subject: RMK closing tree to patches *this* weekend
Date: Fri, 14 May 2010 10:09:36 +0800 [thread overview]
Message-ID: <AANLkTile3zyNe8KaR-TystcZmaNznV2H9WlAWNpddnx_@mail.gmail.com> (raw)
In-Reply-To: <20100513230201.GA26822@n2100.arm.linux.org.uk>
2010/5/14 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> As of the end of this coming weekend, I'll stop taking patches for the
> next merge window. ?I want to tidy up the lose ends which need sorting
> out and give it a decent outing in linux-next for about a week before
> the merge window opens.
>
> So if there's any patches I've missed, please follow up to this email.
If possible, please take the patch:
[PATCH] ARM: fix 'unannotated irqs-on' lockdep warning
which not only fixes the warning and make lockdep available,
but also is more efficient than before if lockdep is enabled:
- remove one calling for asm_trace_hardirqs_on before returning
to user-space
- convert asm_trace_hardirqs_on to trace_hardirqs_on in the
path of returning to kernel space from exception and only call it if
harirqs will be enabled before returning.
Thanks,
--
Lei Ming
next prev parent reply other threads:[~2010-05-14 2:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 23:02 RMK closing tree to patches *this* weekend Russell King - ARM Linux
2010-05-14 0:35 ` Ben Dooks
2010-05-14 9:20 ` Russell King - ARM Linux
2010-05-14 0:58 ` Jassi Brar
2010-05-14 9:24 ` Russell King - ARM Linux
2010-05-14 14:21 ` Jassi Brar
2010-05-14 2:09 ` Ming Lei [this message]
2010-05-14 9:27 ` Russell King - ARM Linux
2010-05-17 9:03 ` Russell King - ARM Linux
2010-05-17 13:04 ` Nicolas Pitre
2010-05-17 13:08 ` Russell King - ARM Linux
2010-05-17 15:10 ` Russell King - ARM Linux
2010-05-17 15:44 ` Will Deacon
2010-05-17 16:18 ` Russell King - ARM Linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTile3zyNe8KaR-TystcZmaNznV2H9WlAWNpddnx_@mail.gmail.com \
--to=tom.leiming@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).