From: drago01 <drago01@gmail.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "Henrique de Moraes Holschuh" <hmh@hmh.eng.br>,
linville@tuxdriver.com, johannes@sipsolutions.net,
yi.zhu@intel.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/3] Introducing IWLAGN
Date: Mon, 21 Jul 2008 15:04:16 +0200 [thread overview]
Message-ID: <f6ca9fed0807210604j5ccb7f1cwb9aaf55132c8ed5c@mail.gmail.com> (raw)
In-Reply-To: <1ba2fa240807210537p66e55407l33662a43e39c106e@mail.gmail.com>
On Mon, Jul 21, 2008 at 2:37 PM, Tomas Winkler <tomasw@gmail.com> wrote:
> On Mon, Jul 21, 2008 at 10:18 AM, Tomas Winkler <tomasw@gmail.com> wrote:
>> On Mon, Jul 21, 2008 at 4:25 AM, Henrique de Moraes Holschuh
>> <hmh@hmh.eng.br> wrote:
>>> On Mon, 21 Jul 2008, Tomas Winkler wrote:
>>>> This series of patches renames iwl4965 driver to iwlagn driver
>>>
>>> Maybe MODULE_ALIAS with the old name would be a good idea?
>>
>> I wasn't aware of this one I'll give it a try. Thanks
>
> It doesn't work much
> if I rename the module name to iwlagn.ko and just add
> MODULE_ALIAS("iwl4965") or alias line in /etc/modprobe.conf. I've
> checked modules.alias it's updated.
> Still modprobe iwl4965 cannot catch it.
> So it's still will create mess when switching between to version of the kernel.
thats odd ... just tested it with a webcam driver (m5602 added
MODULE_ALIAS("bisoncam") and it worked)
does modinfo iwlagn list the alias?
And modprobe.conf should just work (modules.alias is not involved here).
next prev parent reply other threads:[~2008-07-21 13:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 23:40 [PATCH 0/3] Introducing IWLAGN Tomas Winkler
2008-07-20 23:40 ` [PATCH 1/3] iwlwifi: rename iwl4965-base.c to iwl-agn.c Tomas Winkler
2008-07-20 23:40 ` [PATCH 2/3] iwlwifi: fix checkpatch.pl errors Tomas Winkler
2008-07-20 23:40 ` [PATCH 3/3] iwlwifi: rename 4965 to AGN Tomas Winkler
2008-07-21 1:25 ` [PATCH 0/3] Introducing IWLAGN Henrique de Moraes Holschuh
2008-07-21 7:18 ` Tomas Winkler
2008-07-21 12:37 ` Tomas Winkler
2008-07-21 12:59 ` Henrique de Moraes Holschuh
2008-07-21 13:04 ` drago01 [this message]
2008-07-21 13:29 ` Tomas Winkler
2008-07-21 13:45 ` Tomas Winkler
2008-07-21 14:21 ` Dan Williams
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=f6ca9fed0807210604j5ccb7f1cwb9aaf55132c8ed5c@mail.gmail.com \
--to=drago01@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.com \
/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