From: Randy Dunlap <randy.dunlap@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Kees Bakker <kees.bakker@xs4all.nl>,
Keith Packard <keithp@keithp.com>
Subject: [git pull v2] documentation: fix almost duplicate filenames (io/IO-mapping.txt)
Date: Tue, 20 Jul 2010 08:39:40 -0700 [thread overview]
Message-ID: <4C45C33C.9090907@oracle.com> (raw)
In-Reply-To: <AANLkTilwV9PPdpM5JZ65M_TYr_XfVDBHCLXLJVYkTEav@mail.gmail.com>
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rdunlap/linux-docs/ #linuxdocs
for one changeset:
commit f0e4984f0df34e344809c35387d895b57eab5dcc
Author: Randy Dunlap <randy.dunlap@oracle.com>
Date: Mon Jul 19 22:20:27 2010 +0000
Subject: documentation: fix almost duplicate filenames (IO/io-mapping.txt)
From: Randy Dunlap <randy.dunlap@oracle.com>
Having both IO-mapping.txt and io-mapping.txt in Documentation/
was confusing and/or bothersome to some people, so rename
IO-mapping.txt to bus-virt-phys-mapping.txt. Also update
Documentation/00-INDEX for both of these files.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
patch summary:
Documentation/00-INDEX | 6 ++++--
.../{IO-mapping.txt => bus-virt-phys-mapping.txt} | 0
2 files changed, 4 insertions(+), 2 deletions(-)
rename Documentation/{IO-mapping.txt => bus-virt-phys-mapping.txt} (100%)
and thanks for your help.
next prev parent reply other threads:[~2010-07-20 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 1:12 [git pull] documentation: fix almost duplicate filenames (io/IO-mapping.txt) Randy Dunlap
2010-07-20 2:27 ` Linus Torvalds
2010-07-20 5:05 ` Randy Dunlap
2010-07-20 6:59 ` Borislav Petkov
2010-07-20 15:04 ` Linus Torvalds
2010-07-20 15:39 ` Randy Dunlap [this message]
2010-07-20 15:56 ` [git pull v2] " Linus Torvalds
2010-07-20 22:17 ` [git pull v3] " Randy Dunlap
2010-07-20 16:33 ` [git pull v2] " Kees Bakker
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=4C45C33C.9090907@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=kees.bakker@xs4all.nl \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.