From: Douglas Gilbert <dougg@torque.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, Andrew Morton <akpm@osdl.org>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] procfs support for sgiwd93
Date: Mon, 17 Oct 2005 20:55:11 +1000 [thread overview]
Message-ID: <4353830F.3010104@torque.net> (raw)
In-Reply-To: <1129544373.2907.18.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Sat, 2005-10-15 at 02:38 +0100, Ralf Baechle wrote:
>
>>FYI and reviewing pleassure.
>>
>>Author: Thiemo Seufer <ths@networkno.de>
>>Date: Tue Apr 12 14:00:38 2005 +0000
>>
>>Enable proc support, minor code cleanup.
>
>
> isn't this the wrong way around; eg afaik we're deprecating proc support
> from LLDD's...
No more ioctls for LLDDs, no more procfs, just a sysfs
straight jacket; until sysfs goes the way of devfs ...
A subversive thought: a SAS LLDD supporting a SMP target
(as well as the standard SSP,SMP and STP initiators).
Then, via vendor specific SMP functions, control apps
can access the HBA to do things that linux disallows
or makes difficult :-)
[May not work unless HBAs have the equivalent of
the network "lo" interface.]
Doug Gilbert
next prev parent reply other threads:[~2005-10-17 10:54 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 [this message]
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
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=4353830F.3010104@torque.net \
--to=dougg@torque.net \
--cc=akpm@osdl.org \
--cc=arjan@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 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).