From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 03/12] dtb: amd: Fix DMA ranges in device tree
Date: Wed, 10 Feb 2016 22:19:51 +0100 [thread overview]
Message-ID: <5986200.Q9dxHf9bIM@wuerfel> (raw)
In-Reply-To: <56BBA80E.6090205@amd.com>
On Thursday 11 February 2016 04:13:50 Suravee Suthikulpanit wrote:
>
> On 2/9/16 21:57, Arnd Bergmann wrote:
> > On Monday 08 February 2016 11:59:08 Suravee Suthikulpanit wrote:
> >> From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
> >>
> >> Fix DMA ranges of smb0 and pcie0 nodes in AMD Seattle SOC.
> >>
> >> Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
> >>
> >
> > This could use a changelog text to explain why it's broken and how the
> > fix works.
> >
> > Arnd
> >
>
> So, I have not experience the breakage. However, IIUC, the GICv2m MSI
> frame is also considered DMA-able. So, I think it should be included in
> the dma-range specified here. Please let me know if my assumption is
> incorrect. Otherwise, I will include more description in the commit log
> in my next rev.
No, I think this makes sense. Just put a more explanation into the changelog
when those things are not obvious from looking at the change.
Arnd
next prev parent reply other threads:[~2016-02-10 21:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 17:59 [PATCH V2 00/12] dtb: amd: Miscelleneous Updates for AMD Seattle DTS Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 01/12] MAINTAINERS: Adding Maintainers for AMD Seattle Device Tree Suravee Suthikulpanit
2016-02-08 21:38 ` Olof Johansson
2016-02-09 19:49 ` Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 02/12] dtb: amd: Fix GICv2 hypervisor and virtual interface sizes Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 03/12] dtb: amd: Fix DMA ranges in device tree Suravee Suthikulpanit
2016-02-09 14:57 ` Arnd Bergmann
2016-02-10 21:13 ` Suravee Suthikulpanit
2016-02-10 21:19 ` Arnd Bergmann [this message]
2016-02-11 21:23 ` Olof Johansson
2016-02-11 22:59 ` Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 04/12] dtb: amd: Fix typo in SPI device nodes Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 05/12] dtb: amd: Misc changes for I2C " Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 06/12] dtb: amd: Misc changes for SATA device tree nodes Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 07/12] dtb: amd: Misc changes for GPIO devices Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 08/12] dtb: amd: Add PERF CCN-504 device tree node Suravee Suthikulpanit
2016-02-09 14:58 ` Arnd Bergmann
2016-02-09 23:35 ` Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 09/12] dtb: amd: Add KCS " Suravee Suthikulpanit
2016-02-09 14:59 ` Arnd Bergmann
2016-02-09 15:47 ` Brijesh Singh
2016-02-09 16:00 ` Arnd Bergmann
2016-02-09 16:11 ` Brijesh Singh
2016-02-08 17:59 ` [PATCH V2 10/12] dtb: amd: Add AMD XGBE device tree file Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 11/12] dtb: amd: Add support for new AMD Overdrive boards Suravee Suthikulpanit
2016-02-08 17:59 ` [PATCH V2 12/12] dtb: amd: Add support for AMD/Linaro 96Boards Enterprise Edition Server board Suravee Suthikulpanit
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=5986200.Q9dxHf9bIM@wuerfel \
--to=arnd@arndb.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