From: Paul Mackerras <paulus@samba.org>
To: galak@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Fix DMA nodes in the MPC8610 HPCD device tree
Date: Sat, 31 May 2008 15:27:30 +1000 [thread overview]
Message-ID: <18496.57794.862854.470430@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <1212185525-20944-1-git-send-email-timur@freescale.com>
Timur Tabi writes:
> The node for DMA2 in the MPC8610 HPCD device tree has the wrong compatible
> properties. This breaks the DMA driver and the sound driver.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
>
> I have no idea how I let this bug slip in, but this is a must-fix for 2.6.26.
Kumar, do you have anything else for 2.6.26 at the moment? If not,
and this patch is OK with you, I'll put it in along with Olof's two
patches and send them to Linus.
Does anyone else have any pending fixes for 2.6.26?
Paul.
next prev parent reply other threads:[~2008-05-31 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 22:12 [PATCH] Fix DMA nodes in the MPC8610 HPCD device tree Timur Tabi
2008-05-31 5:27 ` Paul Mackerras [this message]
2008-05-31 6:04 ` Kumar Gala
2008-05-31 18:22 ` Josh Boyer
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=18496.57794.862854.470430@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).