public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Tejun Heo <tj@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Nao Nishijima <nao.nishijima.xt@hitachi.com>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Alan Cox <alan@linux.intel.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] block: Revert "[SCSI] genhd: add a new attribute "alias" in gendisk"
Date: Wed, 9 Nov 2011 20:51:57 +0100	[thread overview]
Message-ID: <20111109195157.GN16397@nb.net.home> (raw)
In-Reply-To: <1320859800.8294.27.camel@dabdike.int.hansenpartnership.com>

On Wed, Nov 09, 2011 at 11:30:00AM -0600, James Bottomley wrote:
> On Wed, 2011-11-09 at 08:25 -0800, Tejun Heo wrote:
> > This reverts commit a72c5e5eb738033938ab30d6a634b74d1d060f10.
[...]
> No, I can't agree with this ... if you propose a working alternative,
> I'm listening, but in the absence of one, I think the hack fills a gap

 "The hack fills a gap" -- the definitive guide to Operation System
 API designing by James Bottomley; ISBN-666-666.

 ;-)

 If you open this Pandora's box then one day end-users will ask for
 the feature in all userspace utils. It's not about printk() only,
 it's about aliases for block devices. It's pretty invasive from
 long-term point of view...

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  parent reply	other threads:[~2011-11-09 19:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 16:25 [PATCH] block: Revert "[SCSI] genhd: add a new attribute "alias" in gendisk" Tejun Heo
2011-11-09 16:53 ` Greg KH
2011-11-09 17:19   ` Kay Sievers
2011-11-09 17:30 ` James Bottomley
2011-11-09 17:36   ` Greg KH
2011-11-09 17:38   ` Kay Sievers
2011-11-09 19:51   ` Karel Zak [this message]
2011-11-09 18:54 ` Jens Axboe
2011-11-10 21:21 ` Jeff Garzik
2011-11-11 14:50 ` Nao Nishijima
2011-11-11 17:36   ` Greg KH
2011-11-11 19:09     ` Douglas Gilbert
2011-11-24 12:21 ` Bernd Schubert

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=20111109195157.GN16397@nb.net.home \
    --to=kzak@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alan@linux.intel.com \
    --cc=axboe@kernel.dk \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nao.nishijima.xt@hitachi.com \
    --cc=tj@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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