From: Rusty Russell <rusty@rustcorp.com.au>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Christoph Hellwig <hch@infradead.org>,
"Heinzmann, Robert" <Heinzmann@cc-dresden.de>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] sym53c8xx module parameter passing not working (2.5.6)
Date: Fri, 08 Oct 2004 12:29:16 +1000 [thread overview]
Message-ID: <1097202556.9363.16.camel@localhost.localdomain> (raw)
In-Reply-To: <20041008013029.GM16153@parcelfarce.linux.theplanet.co.uk>
On Fri, 2004-10-08 at 11:30, Matthew Wilcox wrote:
> On Fri, Oct 01, 2004 at 05:55:55PM +0100, Matthew Wilcox wrote:
> to allow people to switch over. But when I try this, I get:
>
> sym53c8xx: Unknown parameter `hostid'
> sym53c8xx: Ignoring new-style parameters in presence of obsolete ones
>
> It'd be nice to be able to use either for a while. Rusty, is there any
> chance of allowing this?
Well, it'd never be neat. I'd rather encourage migration: in 2.6.10 I
will start my jihad on MODULE_PARM, ideally finished before 2.6.11.
It's usually better that someone who knows the code does the transition
(you can often do better than a naive substitution), so my first step
might be to clean up Linus' compile, then make MODULE_PARM warn, to
encourage people to help.
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
next prev parent reply other threads:[~2004-10-08 2:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 15:26 [PATCH] sym53c8xx module parameter passing not working (2.5.6) Heinzmann, Robert
2004-10-01 15:29 ` Christoph Hellwig
2004-10-01 16:55 ` Matthew Wilcox
2004-10-08 1:30 ` Matthew Wilcox
2004-10-08 2:29 ` Rusty Russell [this message]
2004-10-08 14:39 ` New-style module parameters in SCSI drivers Matthew Wilcox
2004-10-01 21:11 ` [PATCH] sym53c8xx module parameter passing not working (2.5.6) Matthew Wilcox
2004-10-01 21:28 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2004-10-01 15:45 Heinzmann, Robert
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=1097202556.9363.16.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=Heinzmann@cc-dresden.de \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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