linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm64 topology support
Date: Fri, 20 Dec 2013 18:07:06 +0000	[thread overview]
Message-ID: <20131220180706.GQ25477@arm.com> (raw)
In-Reply-To: <1387483575-11430-1-git-send-email-broonie@kernel.org>

Hi Mark,

On Thu, Dec 19, 2013 at 08:06:11PM +0000, Mark Brown wrote:
> Another spin of the arm64 topology work - this should incorporate most
> of the feedback from Lorenzo, there's a few things that were still under
> discussion the main ones being:

We'll have to leave this patchset for early January, hopefully we have a
bit of time to review before the merging window. I (and Will, Lorenzo)
am on holiday until around 6th of January.

Have a Good Christmas!

-- 
Catalin

  parent reply	other threads:[~2013-12-20 18:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 20:06 [PATCH 0/4] arm64 topology support Mark Brown
2013-12-19 20:06 ` [PATCH 1/4] arm64: topology: Implement basic CPU " Mark Brown
2013-12-19 20:06 ` [PATCH 2/4] arm64: topology: Add support for topology DT bindings Mark Brown
2013-12-19 20:06 ` [PATCH 3/4] arm64: topology: Tell the scheduler about the relative power of cores Mark Brown
2014-01-07 13:05   ` Lorenzo Pieralisi
2014-01-07 13:38     ` Mark Brown
2014-01-07 14:29       ` Lorenzo Pieralisi
2014-01-07 15:06         ` Mark Brown
2014-01-07 17:56           ` Lorenzo Pieralisi
2014-01-07 18:02             ` Mark Brown
2013-12-19 20:06 ` [PATCH 4/4] arm64: topology: Provide relative power numbers for cores Mark Brown
2013-12-20 18:07 ` Catalin Marinas [this message]
2014-01-07 18:05 ` [PATCH 0/4] arm64 topology support Lorenzo Pieralisi
2014-01-07 18:23   ` Mark Brown
2014-01-07 18:46     ` Mark Brown
2014-01-08 10:15       ` Lorenzo Pieralisi
2014-01-08 10:24     ` Lorenzo Pieralisi
2014-01-08 11:58       ` Mark Brown

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=20131220180706.GQ25477@arm.com \
    --to=catalin.marinas@arm.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).