From: "John W. Linville" <linville@tuxdriver.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: netdev@oss.sgi.com, Linux kernel <linux-kernel@vger.kernel.org>,
jgarzik@pobox.com, romieu@fr.zoreil.com
Subject: Re: [patch 2.6.9 9/11] r8169: Add MODULE_VERSION
Date: Wed, 20 Oct 2004 15:59:38 -0400 [thread overview]
Message-ID: <20041020155938.T8775@tuxdriver.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410201629120.6918@chaos.analogic.com>; from root@chaos.analogic.com on Wed, Oct 20, 2004 at 04:34:45PM -0400
On Wed, Oct 20, 2004 at 04:34:45PM -0400, Richard B. Johnson wrote:
>
> This makes warning error about :
>
> Warning: could not find versions for .tmp_versions/r8169.mod
>
> Do I have to enable something in .config (like CONFIG_MODVERSIONS)?
> If so, how does one make this transparent, to get rid of the
> warning if CONFIG_MODVERSIONS is not set?
Odd...I don't get any such warning, with or without
CONFIG_MODVERSIONS...
MODULE_VERSION is used elsewhere -- do you get that warning
from any other modules? Was this from a clean build?
Send me your .config, and I'll look into it.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2004-10-20 19:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 18:11 [patch 2.6.9 0/11] Add MODULE_VERSION to several network drivers John W. Linville
2004-10-20 18:14 ` [patch 2.6.9 1/11] tg3: Add MODULE_VERSION John W. Linville
2004-10-20 18:33 ` John W. Linville
2004-10-21 4:24 ` David S. Miller
2004-10-20 18:15 ` [patch 2.6.9 2/11] e100: " John W. Linville
2004-10-20 18:34 ` John W. Linville
2004-10-20 18:16 ` [patch 2.6.9 3/11] e1000: " John W. Linville
2004-10-20 18:35 ` John W. Linville
2004-10-20 18:17 ` [patch 2.6.9 4/11] b44: " John W. Linville
2004-10-20 18:36 ` John W. Linville
2004-10-21 4:25 ` David S. Miller
2004-10-20 18:20 ` [patch 2.6.9 5/11] tulip: " John W. Linville
2004-10-20 18:21 ` [patch 2.6.9 6/11] 3c59x: " John W. Linville
2004-10-20 18:23 ` [patch 2.6.9 7/11] 8139too: " John W. Linville
2004-10-20 18:27 ` [patch 2.6.9 8/11] ns83820: " John W. Linville
2004-10-20 18:28 ` [patch 2.6.9 9/11] r8169: " John W. Linville
2004-10-20 20:34 ` Richard B. Johnson
2004-10-20 19:59 ` John W. Linville [this message]
2004-10-21 12:33 ` Richard B. Johnson
2004-10-20 18:29 ` [patch 2.6.9 10/11] bonding: " John W. Linville
2004-10-20 18:32 ` [patch 2.6.9 11/11] vlan: " John W. Linville
2004-10-21 9:17 ` [patch 2.6.9 0/11] Add MODULE_VERSION to several network drivers Arjan van de Ven
2004-10-21 12:22 ` John W. Linville
2004-10-21 13:46 ` Arjan van de Ven
2004-10-21 12:55 ` John W. Linville
2004-10-21 14:11 ` Arjan van de Ven
2004-10-21 13:33 ` John W. Linville
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=20041020155938.T8775@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.com \
--cc=root@chaos.analogic.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;
as well as URLs for NNTP newsgroup(s).