From: Christoph Hellwig <hch@lst•de>
To: Rob Herring <robh+dt@kernel•org>
Cc: "Robin Murphy" <robin.murphy@arm•com>,
"Frank Rowand" <frowand.list@gmail•com>,
"devicetree@vger•kernel.org" <devicetree@vger•kernel.org>,
"linux-arm-kernel@lists•infradead.org"
<linux-arm-kernel@lists•infradead.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"Christoph Hellwig" <hch@lst•de>,
"Marek Szyprowski" <m.szyprowski@samsung•com>,
"Stefan Wahren" <stefan.wahren@i2se•com>,
"Andreas Färber" <afaerber@suse•de>,
"Hans Verkuil" <hverkuil@xs4all•nl>,
"Johan Hovold" <johan@kernel•org>,
linuxppc-dev <linuxppc-dev@lists•ozlabs.org>
Subject: Re: [PATCH 2/2] of: Restrict DMA configuration
Date: Fri, 25 Aug 2017 16:54:57 +0200 [thread overview]
Message-ID: <20170825145457.GA17842@lst.de> (raw)
In-Reply-To: <CAL_Jsq+pDHbrpLDYUVu22tk4OtR9Di4vxZUozwWJDu2ebYSBdg@mail.gmail.com>
On Tue, Aug 15, 2017 at 09:19:50AM -0500, Rob Herring wrote:
> > For the immediate issue at hand, I guess the alternative plan of attack
> > would be to stick a flag in struct bus_type for the bus drivers
> > themselves to opt into generic DMA configuration. That at least keeps
> > everything within the kernel (and come to think of it probably works
> > neatly for modular bus types as well).
>
> I'm fine with the change as is, it's really just the commit text I'm
> commenting on.
Robin, can you resend this with an updated commit text?
prev parent reply other threads:[~2017-08-25 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0819179085df6c41c70e83a2c5c138b95c0386b3.1502468875.git.robin.murphy@arm.com>
[not found] ` <82633e62b64e28dc18bc466319065b92faf2414f.1502468875.git.robin.murphy@arm.com>
2017-08-14 20:08 ` [PATCH 2/2] of: Restrict DMA configuration Rob Herring
2017-08-15 10:18 ` Robin Murphy
2017-08-15 14:19 ` Rob Herring
2017-08-25 14:54 ` Christoph Hellwig [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=20170825145457.GA17842@lst.de \
--to=hch@lst$(echo .)de \
--cc=afaerber@suse$(echo .)de \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=frowand.list@gmail$(echo .)com \
--cc=hverkuil@xs4all$(echo .)nl \
--cc=johan@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=robh+dt@kernel$(echo .)org \
--cc=robin.murphy@arm$(echo .)com \
--cc=stefan.wahren@i2se$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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