From: Adam Jackson <ajax@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: arnd@arndb.de, gregkh@linuxfoundation.org
Subject: [PATCH 2/2] char/mem: Schedule /dev/port for removal
Date: Tue, 7 Feb 2012 09:11:41 -0500 [thread overview]
Message-ID: <1328623901-20628-2-git-send-email-ajax@redhat.com> (raw)
In-Reply-To: <1328623901-20628-1-git-send-email-ajax@redhat.com>
Signed-off-by: Adam Jackson <ajax@redhat.com>
---
Documentation/feature-removal-schedule.txt | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index a0ffac0..c8504f0 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -524,3 +524,16 @@ Files: arch/arm/mach-at91/at91cap9.c
Why: The code is not actively maintained and platforms are now hard to find.
Who: Nicolas Ferre <nicolas.ferre@atmel.com>
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
+
+----------------------------
+
+What: /dev/port
+When: February 2013
+Files: drivers/char/mem.c
+Why: This interface does not match either ISA or PCI semantics for I/O
+ port access. Regardless of the cycle size requested by userspace
+ /dev/port will emit byte-wide reads or writes, which is wrong
+ since devices may not allow byte access or may have side effects
+ when doing byte access to word or dword registers. Use /dev/io
+ instead.
+Who: Adam Jackson <ajax@redhat.com>
--
1.7.7.6
next prev parent reply other threads:[~2012-02-07 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 14:11 [PATCH 1/2] char/mem: Add /dev/io Adam Jackson
2012-02-07 14:11 ` Adam Jackson [this message]
2012-02-07 23:39 ` [PATCH 1/2] char/mem: Add /dev/io (v2) Adam Jackson
2012-02-08 0:17 ` Alan Cox
2012-02-08 0:38 ` Adam Jackson
2012-02-08 9:26 ` Alan Cox
2012-02-08 14:03 ` Adam Jackson
2012-02-08 14:32 ` Alan Cox
2012-02-08 23:16 ` Adam Jackson
2012-02-09 11:27 ` Alan Cox
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=1328623901-20628-2-git-send-email-ajax@redhat.com \
--to=ajax@redhat.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--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 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).