From: dirk.behme@googlemail.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: CONFIG_SMP: Status of pending patches?
Date: Thu, 04 Feb 2010 17:47:12 +0100 [thread overview]
Message-ID: <4B6AFA10.9060004@googlemail.com> (raw)
Regarding two of Catalin's CONFIG_SMP patches in linux-arm git, I
wonder what's the recent status regarding mainline inclusion? The two
patches
1. Global ASID allocation on SMP
http://www.linux-arm.org/git?p=linux-2.6.git;a=commit;h=33618544e3151700950707c920ea2f7ec3e0b7ba
2. ARM: Implement read/write for ownership in the ARMv6 DMA cache ops
http://www.linux-arm.org/git?p=linux-2.6.git;a=commit;h=1bb211d4b81d65760d6befb17a01348db79459b1
seem to be essential for SMP stability.
Patch (1) is marked as applied [1]. Will it be part of final 2.6.33?
For patch (2) I couldn't find anything. Is planned for mainline
inclusion, too?
Sorry if I missed anything.
Thanks
Dirk
[1] http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=5905/1
next reply other threads:[~2010-02-04 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 16:47 Dirk Behme [this message]
2010-02-04 17:02 ` CONFIG_SMP: Status of pending patches? 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=4B6AFA10.9060004@googlemail.com \
--to=dirk.behme@googlemail.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