From: Andy Shevchenko <andy.shevchenko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2/2] dma-mapping: move all DMA mapping code to kernel/dma
Date: Thu, 14 Jun 2018 15:13:46 +0300 [thread overview]
Message-ID: <CAHp75Vcpmx=GLU087Et+LA0_LOCF-xu1beKzb4iLxoOOi91Qmg@mail.gmail.com> (raw)
In-Reply-To: <20180614120029.27315-3-hch-jcswGhMUV9g@public.gmane.org>
On Thu, Jun 14, 2018 at 3:00 PM, Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org> wrote:
> Currently the code is split over various files with dma- prefixes in the
> lib/ and drives/base directories, and the number of files keeps growing.
> Move them into a single directory to keep the code together and remove
> the file name prefixes. To match the irq infrastructure this directory
> is placed under the kernel/ directory.
For my point of view, makes sense!
> +config HAS_DMA
> + bool
> + depends on !NO_DMA
> + default y
I see it's just move from other file, though we might switch to
def_bool y
instead of two lines.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2018-06-14 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 12:00 [RFC] move dma mapping code to kernel/dma Christoph Hellwig
2018-06-14 12:00 ` [PATCH 1/2] dma-mapping: use obj-y instead of lib-y for generic dma ops Christoph Hellwig
2018-06-14 12:00 ` [PATCH 2/2] dma-mapping: move all DMA mapping code to kernel/dma Christoph Hellwig
[not found] ` <20180614120029.27315-3-hch-jcswGhMUV9g@public.gmane.org>
2018-06-14 12:13 ` Andy Shevchenko [this message]
2018-06-14 12:25 ` Christoph Hellwig
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='CAHp75Vcpmx=GLU087Et+LA0_LOCF-xu1beKzb4iLxoOOi91Qmg@mail.gmail.com' \
--to=andy.shevchenko-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).