All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Jon Corbet <corbet@lwn.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: mv DMA-* to separate DMA/ subdirectory
Date: Tue, 3 Jun 2008 19:57:10 +0200	[thread overview]
Message-ID: <20080603175302.GA5910@joi> (raw)
In-Reply-To: <20080602195439.GA27583@fieldses.org>

On Mon, Jun 02, 2008 at 03:54:39PM -0400, J. Bruce Fields wrote:
> From: J. Bruce Fields <bfields@citi.umich.edu>
> 
> Every now and then as I'm looking for something in Documentation/ I get
> annoyed at how cluttered that directory is, and go look for a few files
> that could be grouped into a subdirectory.  This seemed like one
> candidate, though a lot of referenes to DMA-mapping.txt require fixing.
> 
> Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
> ---
> 
> A Documentation/arch directory would take out another dozen entries or
> so, but I haven't had the energy.--b.
> 
>  Documentation/00-INDEX               |    4 -
>  Documentation/DMA-API.txt            |  614 ---------------------------
>  Documentation/DMA-ISA-LPC.txt        |  151 -------
>  Documentation/DMA-attributes.txt     |   24 -
>  Documentation/DMA-mapping.txt        |  766 ----------------------------------
>  Documentation/DMA/00-INDEX           |   10 +
>  Documentation/DMA/DMA-API.txt        |  614 +++++++++++++++++++++++++++
>  Documentation/DMA/DMA-ISA-LPC.txt    |  151 +++++++
>  Documentation/DMA/DMA-attributes.txt |   24 +
>  Documentation/DMA/DMA-mapping.txt    |  766 ++++++++++++++++++++++++++++++++++
>  Documentation/IO-mapping.txt         |    2 +-
>  Documentation/PCI/pci.txt            |    6 +-
>  Documentation/block/biodoc.txt       |    5 +-
>  Documentation/memory-barriers.txt    |    2 +-
>  Documentation/usb/dma.txt            |   13 +-
>  arch/ia64/hp/common/sba_iommu.c      |   12 +-
>  arch/ia64/sn/pci/pci_dma.c           |    4 +-
>  arch/parisc/kernel/pci-dma.c         |    2 +-
>  arch/x86/kernel/pci-gart_64.c        |    2 +-
>  drivers/net/tehuti.c                 |    2 +-
>  drivers/parisc/sba_iommu.c           |   18 +-
>  include/asm-ia64/dma-mapping.h       |    2 +-
>  include/asm-parisc/dma-mapping.h     |    2 +-
>  include/asm-x86/dma-mapping.h        |    2 +-
>  include/linux/dma-attrs.h            |    2 +-
>  include/media/videobuf-dma-sg.h      |    2 +-
>  26 files changed, 1605 insertions(+), 1597 deletions(-)
>  delete mode 100644 Documentation/DMA-API.txt
>  delete mode 100644 Documentation/DMA-ISA-LPC.txt
>  delete mode 100644 Documentation/DMA-attributes.txt
>  delete mode 100644 Documentation/DMA-mapping.txt
>  create mode 100644 Documentation/DMA/00-INDEX
>  create mode 100644 Documentation/DMA/DMA-API.txt
>  create mode 100644 Documentation/DMA/DMA-ISA-LPC.txt
>  create mode 100644 Documentation/DMA/DMA-attributes.txt
>  create mode 100644 Documentation/DMA/DMA-mapping.txt

Maybe drop DMA- prefix? It's useless now.

Marcin

      reply	other threads:[~2008-06-03 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 19:54 [PATCH] Documentation: mv DMA-* to separate DMA/ subdirectory J. Bruce Fields
2008-06-03 17:57 ` Marcin Slusarz [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=20080603175302.GA5910@joi \
    --to=marcin.slusarz@gmail.com \
    --cc=bfields@fieldses.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.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 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.