public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add L2 cache topology to ARM Ltd boards/models
Date: Wed, 25 Feb 2015 17:14:09 +0100	[thread overview]
Message-ID: <2231708.1y1gnmyPQn@wuerfel> (raw)
In-Reply-To: <54EC9546.50005@arm.com>

On Tuesday 24 February 2015 15:14:14 Sudeep Holla wrote:
> Hi Arnd,
> 
> On 21/01/15 14:43, Arnd Bergmann wrote:
> > On Wednesday 21 January 2015 12:02:30 Sudeep Holla wrote:
> >>
> >> Hi Arnd/Olof,
> >>
> >> Though this patch and commit 5d425c18653731af6 ("arm64: kernel: add
> >> support for cpu cache information") which is in -next(via arm64) are
> >> dependent to provide desired functionality, then can go indepedently
> >> if you think there could be conflicts if this change is taken via arm64.
> >> If not, Catalin can pick up with your acks after the review.
> >
> > I think it would be better to take this through arm-soc. It's not
> > extremely likely to cause conflicts, but as you say there are no
> > strict dependencies on which goes in first, so there is no harm
> > in merging them separately.
> >
> 
> I think this patch got missed for -rc1. The arm64 architectural
> support patch for cacheinfo got merged via arm64 tree. It would be good
> if this is also merged so that cache information can be exposed
> to the user-space on ARM Ltd boards.
> 

Ah, bummer. I've applied this one as a fix for 4.0 because I said we'd
take it and dropped the ball on it.

	Arnd

  reply	other threads:[~2015-02-25 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 12:02 [PATCH] arm64: Add L2 cache topology to ARM Ltd boards/models Sudeep Holla
2015-01-21 14:43 ` Arnd Bergmann
2015-01-21 15:48   ` Catalin Marinas
2015-02-24 15:14   ` Sudeep Holla
2015-02-25 16:14     ` Arnd Bergmann [this message]
2015-02-25 18:19       ` Sudeep Holla
2015-01-21 16:46 ` Mark Rutland
2015-02-12 14:07   ` Mark Rutland
2015-02-13  2:52     ` Lorenzo Pieralisi
2015-02-16  9:56     ` Sudeep Holla
2015-02-16 10:19       ` Mark Rutland

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=2231708.1y1gnmyPQn@wuerfel \
    --to=arnd@arndb.de \
    --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