From: Greg KH <greg@kroah.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Nao Nishijima <nao.nishijima.xt@hitachi.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
jcm@redhat.com, dle-develop@lists.sourceforge.net,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
yrl.pp-manager.tt@hitachi.com, dgilbert@interlog.com,
stefanr@s5r6.in-berlin.de, hare@suse.de
Subject: Re: [RFC PATCH 0/4] Persistent device name using alias name
Date: Fri, 8 Jul 2011 09:32:19 -0700 [thread overview]
Message-ID: <20110708163219.GB2646@kroah.com> (raw)
In-Reply-To: <1310141857.3282.87.camel@mulgrave>
On Fri, Jul 08, 2011 at 11:17:36AM -0500, James Bottomley wrote:
> On Fri, 2011-07-08 at 09:04 -0700, Greg KH wrote:
> > Do you seriously think that this sysfs attribute can be removed someday
> > in the future if we get structured logging implemented? It can't,
> > sorry, people will start depending on this and their jury-rigged
> > implementations will require it no matter what we do otherwise.
>
> Yes, it can. The way we do that is to make udev the interface to this
> and the sysfs file becomes an internal udev implementation, not an
> external ABI.
No, sorry, you just described the "external" abi in the
Documentation/ABI directory.
> Any program using it rather than udev that breaks, well, tough, it
> used the wrong interface.
Again, no, we can't do that as you should well know.
And see Kay's response as to how udev will not be using this interface
by default anyway, so I don't see how you will ever be able to remove
this sysfs file once it is added.
greg k-h
next prev parent reply other threads:[~2011-07-08 16:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 8:45 [RFC PATCH 0/4] Persistent device name using alias name Nao Nishijima
2011-07-08 8:46 ` [RFC PATCH 1/4] block: add a new attribute "alias name" in gendisk structure Nao Nishijima
2011-07-08 8:46 ` [RFC PATCH 2/4] sd: modify printk for alias_name Nao Nishijima
2011-07-09 5:42 ` [PATCH] scsi: Make functions out of logging macros Joe Perches
2011-07-09 13:32 ` Nao Nishijima
2011-07-08 8:46 ` [RFC PATCH 3/4] fs: modify disk_name() for alias name Nao Nishijima
2011-07-08 8:46 ` [RFC PATCH 4/4] sd: cleanup " Nao Nishijima
2011-07-08 14:54 ` [RFC PATCH 0/4] Persistent device name using " Greg KH
2011-07-08 15:41 ` Kay Sievers
2011-07-08 15:47 ` Greg KH
2011-07-08 15:54 ` James Bottomley
2011-07-08 16:04 ` Greg KH
2011-07-08 16:17 ` James Bottomley
2011-07-08 16:32 ` Greg KH [this message]
2011-07-08 16:15 ` Kay Sievers
2011-07-08 16:38 ` Kay Sievers
2011-07-11 11:47 ` Hannes Reinecke
2011-07-09 6:11 ` Masami Hiramatsu
2011-08-03 17:16 ` Borislav Petkov
2011-08-10 2:01 ` Masami Hiramatsu
2011-07-08 19:45 ` Karel Zak
2011-07-08 19:58 ` Greg KH
2011-07-15 6:55 ` Nao Nishijima
2011-07-15 12:48 ` Karel Zak
2011-07-16 11:40 ` Nao Nishijima
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=20110708163219.GB2646@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dgilbert@interlog.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=hare@suse.de \
--cc=jcm@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=nao.nishijima.xt@hitachi.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=yrl.pp-manager.tt@hitachi.com \
/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