From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Santosh Shilimkar <santosh.shilimkar-l0cyMroinI0@public.gmane.org>
Cc: "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] dma: of: Move the functions under CONFIG_OF_DMA instead of CONFIG_OF
Date: Fri, 28 Feb 2014 16:21:50 +0100 [thread overview]
Message-ID: <5164707.sdmWv7EuCX@wuerfel> (raw)
In-Reply-To: <5310A52E.90908-l0cyMroinI0@public.gmane.org>
On Friday 28 February 2014 10:03:10 Santosh Shilimkar wrote:
> > As of 5fa422c922c25 "dmaengine: move drivers/of/dma.c -> drivers/dma/of-dma.c"
> >
> > which seems to solve the problem already.
> >
> >> I am not sure but we added couple of functions for dma-ranges
> >> and dma-coherent which gets called from generic code.
> >
> > These functions have nothing to do with the dmaengine code though,
> > they should be in a different file.
> >
> Any suggestion on different file ?
drivers/of/platform.c would be my first choice. Possibly a new
drivers/of/dma-mapping.c.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-02-28 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 0:20 [PATCH] dma: of: Move the functions under CONFIG_OF_DMA instead of CONFIG_OF Santosh Shilimkar
2014-02-28 0:27 ` Santosh Shilimkar
2014-02-28 9:23 ` Arnd Bergmann
2014-02-28 14:24 ` Santosh Shilimkar
[not found] ` <53109C1B.2030606-l0cyMroinI0@public.gmane.org>
2014-02-28 14:47 ` Arnd Bergmann
2014-02-28 15:03 ` Santosh Shilimkar
[not found] ` <5310A52E.90908-l0cyMroinI0@public.gmane.org>
2014-02-28 15:21 ` Arnd Bergmann [this message]
2014-02-28 15:25 ` Santosh Shilimkar
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=5164707.sdmWv7EuCX@wuerfel \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=santosh.shilimkar-l0cyMroinI0@public.gmane.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