linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH 2/2] cdrom_id: only mark sr[0-9]* as ID_CDROM
Date: Tue, 27 Apr 2010 17:05:11 +0000	[thread overview]
Message-ID: <20100427170511.GB2250@piware.de> (raw)
In-Reply-To: <1272363960-22836-2-git-send-email-harald@redhat.com>

Hello Harald,

harald@redhat.com [2010-04-27 12:26 +0200]:
> diff --git a/extras/cdrom_id/60-cdrom_id.rules b/extras/cdrom_id/60-cdrom_id.rules
> index 16b3af9..b3109f1 100644
> --- a/extras/cdrom_id/60-cdrom_id.rules
> +++ b/extras/cdrom_id/60-cdrom_id.rules
> @@ -5,7 +5,7 @@ SUBSYSTEM!="block", GOTO="cdrom_end"
>  KERNEL!="sr[0-9]*|xvd*", GOTO="cdrom_end"
>  ENV{DEVTYPE}!="disk", GOTO="cdrom_end"
>  
> -ENV{ID_CDROM}="1"
> +KERNEL="sr[0-9]*", ENV{ID_CDROM}="1"

This would require the distros/platforms (such as some powerpc) which
still use the IDE CD driver to adapt this as well (which shouldn't be
a big deal, but they need to know, since patches to adapt the first
rule might still apply cleanly)

I wonder why we need this at all. cdrom_id already sets ID_CDROM once
it figured out that it is a drive. Was this added for cases where
cdrom_id failed (we recently fixed a ton of bugs in it)? Or for the
case where you build without extras?

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

  reply	other threads:[~2010-04-27 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 10:26 [PATCH 2/2] cdrom_id: only mark sr[0-9]* as ID_CDROM harald
2010-04-27 17:05 ` Martin Pitt [this message]
2010-04-29 13:48 ` Kay Sievers
2010-05-04  7:09 ` Martin Pitt

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=20100427170511.GB2250@piware.de \
    --to=martin.pitt@ubuntu.com \
    --cc=linux-hotplug@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).