From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] MSM fix
Date: Wed, 20 Jul 2011 23:06:15 +0200 [thread overview]
Message-ID: <1989166.1WcWHOXyl7@wuerfel> (raw)
In-Reply-To: <20110720203703.GA4495@huya.qualcomm.com>
On Wednesday 20 July 2011 13:37:03 David Brown wrote:
> I seem to have missed this fix when it was sent out in April.
>
> The following changes since commit 620917de59eeb934b9f8cf35cc2d95c1ac8ed0fc:
>
> Linux 3.0-rc7 (2011-07-11 16:51:52 -0700)
>
> are available in the git repository at:
> git://codeaurora.org/quic/kernel/davidb/linux-msm.git msm-fix
>
> Jeff Ohlstein (1):
> msm: platsmp: actually read core count in get_core_count
>
Hmm, this one seems like it really applies to older kernels as well, so
we can just as well add a cc:stable at kernel.org tag and put it into the
arm-soc/next/fixes branch, right?
Linus has just pulled the 'last arm-soc fixes for 3.0' branch, and I don't
really want to follow up with 'last fix, this time for real' pull request
unless it's for a serious regression.
On a related topic, what's the deal with the msm-core and msm-move-gpio
branches in the same tree? I have the impression that they should be
in arm-soc.git, but I never received a pull request.
The msm-move-gpio branch looks like it wasn't merged into the gpio
tree either, which would be the other logical place, and the msm-core
branch is currently in linux-next but hasn't been updated since April.
Arnd
next prev parent reply other threads:[~2011-07-20 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 20:37 [GIT PULL] MSM fix David Brown
2011-07-20 21:06 ` Arnd Bergmann [this message]
2011-07-20 22:50 ` David Brown
2011-07-20 22:54 ` Russell King - ARM Linux
2011-07-20 23:44 ` David Brown
2011-07-21 14:49 ` Arnd Bergmann
2011-07-21 15:41 ` Russell King - ARM Linux
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=1989166.1WcWHOXyl7@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