From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: Jeff Ohlstein <johlstei@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Steve Muckle <smuckle@codeaurora.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Tony Lindgren <tony@atomide.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCH 2/3] arm: mm: do not set missing flags on ScorpionMP
Date: Fri, 30 Jul 2010 21:20:29 +0100 [thread overview]
Message-ID: <20100730202029.GB15062@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1280509777.4142.3.camel@m0nster>
On Fri, Jul 30, 2010 at 10:09:37AM -0700, Daniel Walker wrote:
> On Fri, 2010-07-30 at 08:19 +0100, Russell King - ARM Linux wrote:
> > Yes, but if its just for this patch, is there much point to a pull
> > request?
>
> I've got some other stuff too .. Jeff Ohlstein sent several patches (one
> of which started this discussion), which are needed for an SMP board
> we've been working on.
Has it been seen on the mailing list?
next prev parent reply other threads:[~2010-07-30 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 18:58 [PATCH 0/3] ARM changes for ScorpionMP support Jeff Ohlstein
2010-07-23 18:58 ` [PATCH 1/3] arm: Kconfig option for ARCH_MSM_SCORPIONMP Jeff Ohlstein
2010-07-23 18:58 ` [PATCH 2/3] arm: mm: do not set missing flags on ScorpionMP Jeff Ohlstein
2010-07-24 8:23 ` Russell King - ARM Linux
2010-07-28 21:58 ` Daniel Walker
2010-07-28 22:36 ` Russell King - ARM Linux
2010-07-28 22:51 ` Daniel Walker
2010-07-29 7:18 ` Russell King - ARM Linux
2010-07-29 22:42 ` Daniel Walker
2010-07-30 7:19 ` Russell King - ARM Linux
2010-07-30 17:09 ` Daniel Walker
2010-07-30 20:20 ` Russell King - ARM Linux [this message]
2010-07-30 20:46 ` Daniel Walker
2010-07-23 18:58 ` [PATCH 3/3] arm: macros for wfe, sev instructions Jeff Ohlstein
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=20100730202029.GB15062@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=catalin.marinas@arm.com \
--cc=dwalker@codeaurora.org \
--cc=johlstei@codeaurora.org \
--cc=kirill@shutemov.name \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smuckle@codeaurora.org \
--cc=tony@atomide.com \
/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).