From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: topology: Implement basic CPU topology support
Date: Tue, 4 Mar 2014 18:52:27 +0800 [thread overview]
Message-ID: <20140304105227.GM13126@sirena.org.uk> (raw)
In-Reply-To: <20140304102806.GH30596@arm.com>
On Tue, Mar 04, 2014 at 10:28:06AM +0000, Catalin Marinas wrote:
> > I'm totally fine with that, I only made it selectable due to the 32 bit
> > code doing that - I'm not sure we even need the separate symbol.
> > Whatever you prefer.
> Like that?
Looks good to me!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140304/b01453f2/attachment-0001.sig>
next prev parent reply other threads:[~2014-03-04 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 7:51 [PATCH v2] arm64: topology: Implement basic CPU topology support Mark Brown
2014-03-04 9:55 ` Catalin Marinas
2014-03-04 10:16 ` Mark Brown
2014-03-04 10:28 ` Catalin Marinas
2014-03-04 10:52 ` Mark Brown [this message]
2014-03-04 10:46 ` Lorenzo Pieralisi
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=20140304105227.GM13126@sirena.org.uk \
--to=broonie@kernel.org \
--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).