From: Amit Kale <amitkale@netxen.com>
To: Andi Kleen <ak@suse.de>
Cc: netdev@vger.kernel.org
Subject: Re: NetXen driver name
Date: Mon, 12 Feb 2007 13:33:16 +0530 [thread overview]
Message-ID: <200702121333.16199.amitkale@netxen.com> (raw)
In-Reply-To: <p734ppw349e.fsf@bingen.suse.de>
The already released kernel contains a broken driver. It broke due to some
code rearrangement changes someone submitted to fix sparse warnings.
-Amit
On Thursday 08 February 2007 23:45, Andi Kleen wrote:
> Amit Kale <amitkale@netxen.com> writes:
> > Hi,
> >
> > NetXen ethernet driver present in 2.6.20 has name "netxen_nic". The
> > product itself is refered to as "nx_nic". To make it inline with the
> > product, would it be a good idea to change the name of the driver to
> > "nx_nic"?
>
> When it's already in a released kernel it's a little late to rename the
> module. You would cause upgrade pain to users who have hardcoded the module
> name.
>
> -Andi
next prev parent reply other threads:[~2007-02-12 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 16:22 NetXen driver name Amit Kale
2007-02-08 18:15 ` Andi Kleen
2007-02-12 8:03 ` Amit Kale [this message]
2007-02-12 8:12 ` Andi Kleen
2007-02-12 8:28 ` Amit Kale
2007-02-12 8:47 ` Andi Kleen
2007-02-12 8:29 ` Al Viro
2007-02-12 9:18 ` Amit Kale
2007-02-12 8:29 ` Amit Kale
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=200702121333.16199.amitkale@netxen.com \
--to=amitkale@netxen.com \
--cc=ak@suse.de \
--cc=netdev@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 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).