From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] MSM fix
Date: Wed, 20 Jul 2011 15:50:10 -0700 [thread overview]
Message-ID: <20110720225010.GA18381@huya.qualcomm.com> (raw)
In-Reply-To: <1989166.1WcWHOXyl7@wuerfel>
On Wed, Jul 20, 2011 at 11:06:15PM +0200, Arnd Bergmann wrote:
> 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?
It looks like it would apply to 2.6.38 and 39 as well. I'm not sure
it qualifies under the "It must fix a real bug that bothers people".
It would only apply if someone had set NR_CPUS to more than 2.
> 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.
It's not serious, so 3.1 is fine.
> 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.
I had sent a pull request for msm-move-gpio to Grant, but apparently
that didn't happen. If more appropriate, I can send one to you for
it, or resend to Grant.
The msm-core stuff happened before the snafu about ARM, and I was
holding off on these things. The authors of these patches say they
are working on cleaned up versions.
I'm not sure we want the dummy clocks code in the kernel. It's
intended as a placeholder. Stephen Boyd has a 26-series patch that
adds better clock support. Given the size (13047 insertions), this
may need some cleanup or even device-tree work to include.
Unfortunately, a lot of the Qualcomm development seems to have moved
back to private trees.
BTW, I am planning on being at the Linaro Connect in August.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-07-20 22:50 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
2011-07-20 22:50 ` David Brown [this message]
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=20110720225010.GA18381@huya.qualcomm.com \
--to=davidb@codeaurora.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