From: Deepak Saxena <dsaxena@plexity.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove whitespace from ALI15x3 IDE driver name
Date: Thu, 12 Aug 2004 14:33:01 -0700 [thread overview]
Message-ID: <20040812213301.GA5876@plexity.net> (raw)
In-Reply-To: <1092340343.22362.8.camel@localhost.localdomain>
On Aug 12 2004, at 20:55, Alan Cox was caught saying:
> On Iau, 2004-08-12 at 17:04, Christoph Hellwig wrote:
> > On Thu, Aug 12, 2004 at 06:54:38PM +0000, Pekka Enberg wrote:
> > > This patch removes whitespace from ALI15x3 IDE driver name that appears in the
> > > sysfs directory. It is against 2.6.7.
> >
> > You jnow that this breaks every tool that knew of the names so far? E.g.
> > Debian mkinitrd (now has a patch to deal with both the whitespace and
> > non-whitespace variants) and probably quite a few installers out there.
>
> Greg okayed a pile of other related changes including some that were not
> just white space to _ but changed the actual string. So you may want to
> take it up with Greg rather than Pekka who is just filling in one that
> was missed
Not having touched installer code, can someone enlighten me on
why the installer would break with 's/ /_' or any other change
to driver name?
~Deepak
--
Deepak Saxena - dsaxena at plexity dot net - http://www.plexity.net/
"Unlike me, many of you have accepted the situation of your imprisonment and
will die here like rotten cabbages." - Number 6
next prev parent reply other threads:[~2004-08-12 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 18:54 [PATCH] Remove whitespace from ALI15x3 IDE driver name Pekka Enberg
2004-08-12 16:04 ` Christoph Hellwig
2004-08-12 19:19 ` Pekka Enberg
2004-08-12 19:55 ` Alan Cox
2004-08-12 21:33 ` Deepak Saxena [this message]
2004-08-15 18:09 ` Christoph Hellwig
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=20040812213301.GA5876@plexity.net \
--to=dsaxena@plexity.net \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.