All of lore.kernel.org
 help / color / mirror / Atom feed
From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] Re: net/3c59x: module_param conversions
Date: Thu, 18 Nov 2004 14:22:33 +0000	[thread overview]
Message-ID: <20041118142233.GC5645@nd47.coderock.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

On 18/11/04 14:19 +0100, Steffen Klassert wrote:
> On Tue, Nov 16, 2004 at 07:10:44PM +0100 or thereabouts, Domen Puncer wrote:
> > Convert 3c59x.c to new module parameter api.
> > Variables are moved before module_param*.
> 
> Just a remark,
> the module_param conversion for the 3c59x driver is already in the -mm tree.
> Many people route their patches through -mm, so it is in general a good 
> idea to look whats in -mm before starting to work.

Yeah, it's a good idea for popular conversions.

Anyway, in rc2-mm2:
--- linux-2.6.10-rc2/drivers/net/3c59x.c        2004-11-14 21:05:31.000000000 -0
800
+++ 25/drivers/net/3c59x.c      2004-11-17 23:21:24.184865960 -0800
@@ -277,6 +277,7 @@ MODULE_AUTHOR("Donald Becker <becker@scy
 MODULE_DESCRIPTION("3Com 3c59x/3c9xx ethernet driver "
                                        DRV_VERSION " " DRV_RELDATE);
 MODULE_LICENSE("GPL");
+MODULE_VERSION(DRV_VERSION);
 
 MODULE_PARM(debug, "i");
^^^
Doesn't seem converted.
Maybe you mean via-rhine patches; those are in.


	Domen

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

             reply	other threads:[~2004-11-18 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 14:22 Domen Puncer [this message]
2004-11-18 15:47 ` [KJ] Re: net/3c59x: module_param conversions Steffen Klassert

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=20041118142233.GC5645@nd47.coderock.org \
    --to=domen@coderock.org \
    --cc=kernel-janitors@vger.kernel.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.