From: ccross@android.com (Colin Cross)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra board updates for 2.6.40
Date: Fri, 27 May 2011 09:24:12 -0700 [thread overview]
Message-ID: <BANLkTikFjz6QfsaHsMbzXeLLB8azOcdGBQ@mail.gmail.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0498A4870C@HQMAIL01.nvidia.com>
On Thu, May 26, 2011 at 11:00 AM, Stephen Warren <swarren@nvidia.com> wrote:
> Colin,
>
> You had mentioned not taking any board updates for Tegra for 2.6.40.
>
> Could you please consider taking at least the following one patch:
>
> http://www.spinics.net/lists/linux-tegra/msg01396.html
>
> This is a simple bug-fix rather than new feature etc. Without this,
> audio on Harmony, which previously worked fine, fails to initialize
> due to the conflicting attempted GPIO registrations. (I *think*
> Harmony still boots OK without the fix, but I vaguely remember
> the fix being needed just to boot, but I'm probably wrong about that)
>
> Thanks!
Sure, I can take bug fixes.
parent reply other threads:[~2011-05-27 16:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <74CDBE0F657A3D45AFBB94109FB122FF0498A4870C@HQMAIL01.nvidia.com>]
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=BANLkTikFjz6QfsaHsMbzXeLLB8azOcdGBQ@mail.gmail.com \
--to=ccross@android.com \
--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;
as well as URLs for NNTP newsgroup(s).