This patch goes against 2.5.59 and changes every <modulename>.o to
<modulename>.ko in every Kconfig they occur, except the ones I overlooked ;)
It's a rather large patch so it's gzipped and attached.
--
GertJan
In message <[email protected]> you write:
>
> --------------Boundary-00=_T1W6C6TJ1EXFI4RML77P
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: 8bit
>
> This patch goes against 2.5.59 and changes every <modulename>.o to
> <modulename>.ko in every Kconfig they occur, except the ones I overlooked ;)
> It's a rather large patch so it's gzipped and attached.
I'd prefer just trimming the extension. "modprobe foo" is what they
want to know.
It also sets the prefix of the parameters, when/if they are updated.
Cheers!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
On Wed, 29 Jan 2003, Rusty Russell wrote:
> I'd prefer just trimming the extension. "modprobe foo" is what they
> want to know.
>
> It also sets the prefix of the parameters, when/if they are updated.
I tend to agree with you, but the .o in existing help files is clearly
wrong. Perhaps the patch could be edited to just replace the .ko with
nothing. Yep, it can.
--
bill davidsen <[email protected]>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
On Thursday 30 January 2003 04:05, Bill Davidsen wrote:
> On Wed, 29 Jan 2003, Rusty Russell wrote:
> > I'd prefer just trimming the extension. "modprobe foo" is what they
> > want to know.
> >
> > It also sets the prefix of the parameters, when/if they are updated.
>
> I tend to agree with you, but the .o in existing help files is clearly
> wrong. Perhaps the patch could be edited to just replace the .ko with
> nothing. Yep, it can.
OK, here is a new patch, I edited the old patch and took out the .ko's
so now the extension is trimmed instead.
--
GertJan