From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: George Nychis <gnychis@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: what determines how firmware is loaded? (Q. on request_firmware details)
Date: Thu, 26 Apr 2012 16:48:45 +0100 [thread overview]
Message-ID: <20120426154844.GL3207@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120426152742.GB15674@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Thu, Apr 26, 2012 at 08:27:42AM -0700, Greg KH wrote:
> On Thu, Apr 26, 2012 at 04:23:10PM +0100, Mark Brown wrote:
> > Unfortunately 3.0 is what ICS is based off so the overwhelming majority
> > of vendor code is going to be based on it until the next Android
> > release. With my vendor hat on I have to say that we find our upstream
> > first policy extremely effective so we shouldn't be part of the issue.
> That's great, and understandable, but the original poster said they were
> using an old Ubuntu release, and the ability for the community to
> support bugs in older kernel releases like this is very difficult as you
> well know.
Oh, I missed that bit of the thread - if they're using a desktop distro
then upgrading should be much less painful than it would be with a
typical vendor kernel.
> The next Android release should be "any day now" so hopefully we move on
> from 3.0 soon...
Well, by the end of the summer or something - even when the release
drops there's always lag while the releases propagate out to the wider
market.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-04-26 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 20:18 what determines how firmware is loaded? (Q. on request_firmware details) George Nychis
2012-04-23 21:21 ` Greg KH
2012-04-23 21:28 ` George Nychis
2012-04-23 22:52 ` George Nychis
2012-04-23 22:56 ` Greg KH
2012-04-26 15:23 ` Mark Brown
2012-04-26 15:27 ` Greg KH
2012-04-26 15:48 ` Mark Brown [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=20120426154844.GL3207@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=gnychis@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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