From: Matthew Wilcox <matthew@wil.cx>
To: Jeff Garzik <jeff@garzik.org>
Cc: FUJITA Tomonori <tomof@acm.org>,
James.Bottomley@SteelEye.com, akpm@linux-foundation.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
fujita.tomonori@lab.ntt.co.jp
Subject: Re: queued patches for SCSI for 2.6.24
Date: Tue, 25 Sep 2007 20:56:08 -0600 [thread overview]
Message-ID: <20070926025608.GA3899@parisc-linux.org> (raw)
In-Reply-To: <46F9C5ED.6050505@garzik.org>
On Tue, Sep 25, 2007 at 10:37:33PM -0400, Jeff Garzik wrote:
> Are there any const-ness worries for scsi_host_template, or plans for
> the future? I do not see any other examples of the host template
> members getting modified.
Goodness, Jeff, you haven't looked too hard. There's dozens of examples
I've come across trawling the horrible unmaintained drivers. I'd love
to see scsi_host_template become const, but it's not happening any time
soon, and we can address this little piece when the time comes.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2007-09-26 2:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 1:00 queued patches for SCSI for 2.6.24 James Bottomley
2007-09-26 1:05 ` David Miller
2007-09-26 1:28 ` FUJITA Tomonori
2007-09-26 1:42 ` James Bottomley
2007-09-26 2:12 ` FUJITA Tomonori
2007-09-26 2:37 ` Jeff Garzik
2007-09-26 2:52 ` FUJITA Tomonori
2007-09-26 2:56 ` Matthew Wilcox [this message]
2007-09-26 3:34 ` Jeff Garzik
2007-09-26 3:38 ` Matthew Wilcox
2007-09-26 3:45 ` James Bottomley
2007-09-26 3:55 ` Jeff Garzik
2007-09-26 3:55 ` FUJITA Tomonori
2007-09-26 4:01 ` James Bottomley
2007-09-26 4:10 ` FUJITA Tomonori
2007-09-26 4:56 ` FUJITA Tomonori
2007-09-26 14:07 ` James Bottomley
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=20070926025608.GA3899@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tomof@acm.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