From: Zhu Yi <yi.zhu@intel.com>
To: David Miller <davem@davemloft.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi
Date: Thu, 24 Dec 2009 14:24:56 +0800 [thread overview]
Message-ID: <1261635896.6037.26.camel@debian> (raw)
In-Reply-To: <20091223.215221.191412308.davem@davemloft.net>
On Thu, 2009-12-24 at 13:52 +0800, David Miller wrote:
> From: Zhu Yi <yi.zhu@intel.com>
> Date: Thu, 24 Dec 2009 13:46:07 +0800
>
> > I'm trying allmodconfig on wireless-testing now. It takes some time to
> > finish make. But a simple running "make M=drivers/net/wireless/" twice
> > doesn't show this issue.
> >
>
> It's the include of generated/utsrelease.h by iwl-core.h that causes
> the rebuild.
Thanks. It was first introduced by below commit. And was later changed
to use generated/utsrelease.h. I'm wondering if we should really use
linux/utsrelease.h (or linux/version.h) or remove the kernel version
totally from the driver version (driver compile tag can be remained).
Any suggestions?
Thanks,
-yi
commit 900bb717424e5df12b1ef7ebb017be2a8915b806
Author: Reinette Chatre <reinette.chatre@intel.com>
Date: Wed Dec 2 12:53:01 2009 -0800
iwlwifi: driver version track kernel version
The driver version number is a remnant from when there was an out-of-tree
iwlwifi driver. Now that the driver forms part of kernel source we do not
need a separate driver version. Instead, we now use the kernel version as
driver version. We maintain the previous tags used to indicate which
components the driver has been compiled with.
next prev parent reply other threads:[~2009-12-24 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 5:08 iwlwifi David Miller
2009-12-24 5:46 ` iwlwifi Zhu Yi
2009-12-24 5:52 ` iwlwifi David Miller
2009-12-24 6:24 ` Zhu Yi [this message]
2009-12-24 6:30 ` iwlwifi David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-02-16 0:43 iwlwifi Antonio Quartulli
2008-02-19 22:20 ` iwlwifi Chatre, Reinette
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=1261635896.6037.26.camel@debian \
--to=yi.zhu@intel.com \
--cc=davem@davemloft.net \
--cc=linux-wireless@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).