All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] MCPM maintenance for v4.1
Date: Fri, 3 Apr 2015 12:53:56 -0700	[thread overview]
Message-ID: <20150403195356.GS23023@localhost> (raw)
In-Reply-To: <alpine.LFD.2.11.1503251216310.27567@knanqh.ubzr>

On Wed, Mar 25, 2015 at 12:46:47PM -0400, Nicolas Pitre wrote:
> Please consider pulling the following:
> 
> http://git.linaro.org/people/nicolas.pitre/linux.git mcpm_for_armsoc
> 
> This series greatly simplifies things by moving all the locking handling 
> to the core code, leaving machine specific backend only with simple and 
> straight forward operations performed under lock protection. It will no 
> longer be necessary for backend authors to know about all the MCPM 
> subtleties for their code to be "right".
> 
> To avoid a flag day, the new scheme is introduced in parallel to the 
> existing backend interface. This series may be merged at the same time 
> as new backends still using the previous interface. That old interface 
> should be removed in a subsequent merge cycle after everything is 
> converted over.
> 
> The diffstat also shows a clear benefit.  Despite the addition of new 
> documentation and the previous interface still in place, the number of 
> lines actually goes down.
> 
> Tested on Versatile Express TC2 and Exynos 5800 (Chromebook2).

Hi,

This was based on a newer -rc than any other arm-soc contents (-rc4). I ended
up cherry-picking the patches over instead.

So, contents picked up but I didn't do it by merging the branch.


Thanks,

-Olof

      parent reply	other threads:[~2015-04-03 19:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 16:46 [GIT PULL] MCPM maintenance for v4.1 Nicolas Pitre
2015-04-02 16:49 ` Nicolas Pitre
2015-04-03 19:53 ` Olof Johansson [this message]

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=20150403195356.GS23023@localhost \
    --to=olof@lixom.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.