From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx28: Fix AUART4 TX-DMA interrupt name
Date: Fri, 24 Apr 2015 13:30:20 +0200 [thread overview]
Message-ID: <201504241330.20843.marex@denx.de> (raw)
In-Reply-To: <5539E927.3080205@i2se.com>
On Friday, April 24, 2015 at 08:56:39 AM, Stefan Wahren wrote:
> Hi Marek,
>
> Am 24.04.2015 um 05:16 schrieb Marek Vasut:
> > Fix a typo in the TX DMA interrupt name for AUART4.
> > This patch makes AUART4 operational again.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Shawn Guo <shawn.guo@linaro.org>
> > Cc: stable at vger.kernel.org
> > ---
> >
> > arch/arm/boot/dts/imx28.dtsi | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > NOTE: This bug goes all the way back to at least Linux 3.10
> > NOTE: I am not the author of the patch, but I am not allowed to disclose
> >
> > the name of the original author due to the circumstances.
> >
> > diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
> > index 25e25f8..4e073e8 100644
> > --- a/arch/arm/boot/dts/imx28.dtsi
> > +++ b/arch/arm/boot/dts/imx28.dtsi
> > @@ -913,7 +913,7 @@
> >
> > 80 81 68 69
> > 70 71 72 73
> > 74 75 76 77>;
> >
> > - interrupt-names = "auart4-rx", "aurat4-tx",
"spdif-tx", "empty",
> > + interrupt-names = "auart4-rx", "auart4-tx",
"spdif-tx", "empty",
> >
> > "saif0", "saif1", "i2c0",
"i2c1",
> > "auart0-rx", "auart0-tx",
"auart1-rx", "auart1-tx",
> > "auart2-rx", "auart2-tx",
"auart3-rx", "auart3-tx";
>
> looks good, but shouldn't we patch also the wrong documentation?
>
> Documentation/devicetree/bindings/dma/fsl-mxs-dma.txt
Nice catch, I sent out a fixed V2 patch.
Thank you!
Best regards,
Marek Vasut
prev parent reply other threads:[~2015-04-24 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 3:16 [PATCH] ARM: dts: imx28: Fix AUART4 TX-DMA interrupt name Marek Vasut
2015-04-24 6:56 ` Stefan Wahren
2015-04-24 11:30 ` Marek Vasut [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=201504241330.20843.marex@denx.de \
--to=marex@denx.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;
as well as URLs for NNTP newsgroup(s).