From: Michael Walle <michael@walle.cc>
To: Shawn Guo <shawnguo@kernel.org>
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Li Yang <leoyang.li@nxp.com>,
Peng Ma <peng.ma@nxp.com>
Subject: Re: [PATCH 1/2] dt-bindings: dma: fsl-edma: fix ls1028a-edma compatible
Date: Mon, 11 May 2020 11:08:59 +0200 [thread overview]
Message-ID: <de4a40b03858930c15724302b3bf7bd0@walle.cc> (raw)
In-Reply-To: <20200413141830.GA4722@dragon>
Hi Shawn Guo,
Am 2020-04-13 16:18, schrieb Shawn Guo:
> On Fri, Mar 06, 2020 at 09:54:02PM +0100, Michael Walle wrote:
>> The bootloader will fix up the IOMMU entries only on nodes with the
>> compatible "fsl,vf610-edma". Thus make this compatible string
>> mandatory
>> for the ls1028a-edma.
>>
>> While at it, fix the "fsl,fsl," typo.
>>
>> Signed-off-by: Michael Walle <michael@walle.cc>
>> Fixes: d8c1bdb5288d ("dt-bindings: dma: fsl-edma: add new
>> fsl,fsl,ls1028a-edma")
>
> Applied both. Will try to send for 5.7-rc inclusion.
Are there any news on the inclusion? Unfortunately, I also forgot the
fixes
tag on patch 2/2, so it won't end up in v5.7.x.
-michael
prev parent reply other threads:[~2020-05-11 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 20:54 [PATCH 1/2] dt-bindings: dma: fsl-edma: fix ls1028a-edma compatible Michael Walle
2020-03-06 20:54 ` [PATCH 2/2] arm64: dts: ls1028a: add "fsl,vf610-edma" compatible Michael Walle
2020-03-07 2:09 ` [EXT] " Peng Ma
2020-03-07 9:25 ` Michael Walle
2020-03-07 10:32 ` Peng Ma
2020-03-07 13:10 ` Michael Walle
2020-03-23 14:36 ` Michael Walle
2020-03-23 19:43 ` [PATCH 1/2] dt-bindings: dma: fsl-edma: fix ls1028a-edma compatible Rob Herring
2020-04-13 14:18 ` Shawn Guo
2020-05-11 9:08 ` Michael Walle [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=de4a40b03858930c15724302b3bf7bd0@walle.cc \
--to=michael@walle.cc \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peng.ma@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).