From: Rob Landley <rob@landley.net>
To: Vinod Koul <vinod.koul@intel.com>, hongbo.zhang@freescale.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@redhat.com>,
Richard Henderson <rth@cygnus.com>,
Jakub Jelinek <jakub@redhat.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Arthur Kepner <akepner@sgi.com>,
sumit.semwal@linaro.org, Pierre Ossman <drzeus@drzeus.cx>,
Andy Shevchenko <andriy.shevchenko@linux.jf.intel.com>
Subject: Re: [PATCH resend 1/2] Documentation: move all DMA documentations into Documentaion/dma
Date: Sat, 18 Jan 2014 11:59:13 -0600 [thread overview]
Message-ID: <52DAC0F1.9080202@landley.net> (raw)
In-Reply-To: <20140116155921.GJ25466@intel.com>
On 01/16/14 09:59, Vinod Koul wrote:
> On Thu, Jan 16, 2014 at 06:50:04PM +0800, hongbo.zhang@freescale.com wrote:
>> From: Hongbo Zhang <hongbo.zhang@freescale.com>
>>
>> Since there are already seven DMA documentations under the top Documentation/,
>> it is better to create one dedicated directory for them.
>
> Well the problem is that not everything is same. Some of these mean how to use
> dma mapping API, couple are related to dmaengine, so clubing everything into
> "dma" doesnt sound right to me!
Putting everything in the world in the top level directory isn't all
flowers and kittens either.
Where would be a _better_ place to move one of those files to?
Rob
next prev parent reply other threads:[~2014-01-18 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 10:50 [PATCH resend 1/2] Documentation: move all DMA documentations into Documentaion/dma hongbo.zhang
2014-01-16 10:50 ` [PATCH resend 2/2] Documentation: update some DMA document texts due to relocation hongbo.zhang
2014-01-16 14:29 ` [PATCH resend 1/2] Documentation: move all DMA documentations into Documentaion/dma Andy Shevchenko
2014-01-16 15:59 ` Vinod Koul
2014-01-18 17:59 ` Rob Landley [this message]
2014-01-20 4:29 ` Vinod Koul
2014-01-20 9:12 ` Hongbo Zhang
2014-01-18 17:56 ` Rob Landley
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=52DAC0F1.9080202@landley.net \
--to=rob@landley.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akepner@sgi.com \
--cc=andriy.shevchenko@linux.jf.intel.com \
--cc=davem@redhat.com \
--cc=drzeus@drzeus.cx \
--cc=hongbo.zhang@freescale.com \
--cc=jakub@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@cygnus.com \
--cc=sumit.semwal@linaro.org \
--cc=vinod.koul@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.