public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ari Pollak <compwiz@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: devices.txt inconsistency
Date: Mon, 1 Jan 2001 17:06:54 -0500	[thread overview]
Message-ID: <20010101170654.A5856@sourceware.net> (raw)

This has not been fixed for at least a year that i can remember - in
Documentation/devices.txt, it says /dev/js* should be char-major-15*,
but in Documentation/joystick.txt it says it should be char-major-13.
I'm assuming joystick.txt is the correct one, and devices.txt should be
updated to reflect this.. before 2.4.0 would be nice.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-01 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-01 22:06 Ari Pollak [this message]
2001-01-01 23:24 ` devices.txt inconsistency Robert Read
2001-01-01 23:48   ` H. Peter Anvin
2001-01-02 13:37     ` ratz
2001-01-01 23:35 ` Robert Read
  -- strict thread matches above, loose matches on Subject: below --
2001-01-02 16:19 Douglas Gilbert
2001-01-02 17:29 ` H. Peter Anvin

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=20010101170654.A5856@sourceware.net \
    --to=compwiz@bigfoot.com \
    --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