From: Douglas Gilbert <dougg@torque.net>
To: James.Bottomley@SteelEye.com
Cc: Christoph Hellwig <hch@infradead.org>,
Ralf Baechle <ralf@linux-mips.org>,
linux-scsi@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] procfs support for sgiwd93
Date: Mon, 17 Oct 2005 21:22:48 +1000 [thread overview]
Message-ID: <43538988.3000204@torque.net> (raw)
In-Reply-To: <20051017104312.GB22710@infradead.org>
Christoph Hellwig wrote:
> On Sat, Oct 15, 2005 at 02:38:24AM +0100, Ralf Baechle wrote:
>
>>FYI and reviewing pleassure.
>
>
> NACK, no more new procfs support for scsi driver.
James Bottomley,
Is there any such policy?
Christoph Hellwig previously has used this purported policy
to reject scsi procfs bug fixes:
"[PATCH] scsi: /proc/scsi/scsi patch for large number of devices"
As for alternate tools to 'cat /proc/scsi/scsi', I
am not aware of many distributions using lsscsi (debian
and gentoo do), perhaps there are other tools. I
suspect a lot of folks are still using 'cat /proc/scsi/scsi'.
Does Christoph Hellwig have the right to NACK/veto
etc work that is not his when you are the SCSI maintainer?
Douglas Gilbert
next prev parent reply other threads:[~2005-10-17 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 1:38 [PATCH] procfs support for sgiwd93 Ralf Baechle
2005-10-17 10:19 ` Arjan van de Ven
2005-10-17 10:55 ` Douglas Gilbert
2005-10-17 11:25 ` Arjan van de Ven
2005-10-17 10:43 ` Christoph Hellwig
2005-10-17 10:47 ` Ralf Baechle
2005-10-17 10:49 ` Christoph Hellwig
2005-10-17 11:22 ` Douglas Gilbert [this message]
2005-10-19 21:40 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2005-10-20 18:04 Ralf Baechle
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=43538988.3000204@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ralf@linux-mips.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 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.