mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Marc - A. Dahlhaus" <mad@wol.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix capi devicenames
Date: Thu, 30 Sep 2010 10:30:10 +0100	[thread overview]
Message-ID: <20100930103010.1a6a7785@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <4CA391B3.1030806@wol.de>

On Wed, 29 Sep 2010 21:21:23 +0200
"Marc - A. Dahlhaus" <mad@wol.de> wrote:

> capi device names should get changed to what userspace expects.

If userspace isn't following the spec (which has been the spec for many
years) then thats not our problem.

> Without this change recent udev versions can't produce working device
> nodes as the capi control device node name "capi" collides with the
> "capi" directory under which userspace expects to get the application
> device nodes. This also fixes the Documentation.

The documentation isn't broken, the documentation *is* the reference.

NAK. Fix udev.


We have a spec for a reason, if some distro didn't follow it then that's
up to them but they can sort out their own udev.

Alan

  reply	other threads:[~2010-09-30  9:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 19:21 Marc - A. Dahlhaus
2010-09-30  9:30 ` Alan Cox [this message]
2010-09-30 10:08   ` Kay Sievers
2010-09-30 10:56     ` Alan Cox
2010-09-30 10:37   ` Marc - A. Dahlhaus
2010-09-30 10:50     ` Kay Sievers
2010-09-30 11:29       ` Alan Cox
2010-09-30 12:50         ` Marc - A. Dahlhaus
2010-09-30 17:35           ` Olivier Galibert
2010-09-30 19:20           ` Kay Sievers
2010-10-01  8:02             ` [PATCH] Fix capi devicenames v2 Marc - A. Dahlhaus
2010-10-01  8:36             ` [PATCH] Fix capi devicenames Marc - A. Dahlhaus
2010-10-01  9:20               ` Kay Sievers
2010-09-30 11:35     ` 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=20100930103010.1a6a7785@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mad@wol.de \
    /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

all inboxes | Powered by JetHome®