From: Zhu Yi <yi.zhu@intel.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>, Sam Ravnborg <sam@ravnborg.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Jason Riedy <jason@acm.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH] Allow building iwl3945 without iwl4965.
Date: Wed, 30 Apr 2008 17:34:26 +0800 [thread overview]
Message-ID: <1209548066.2827.42.camel@debian.sh.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0804291934470.18219@shark.he.net>
On Tue, 2008-04-29 at 19:36 -0700, Randy.Dunlap wrote:
> On Wed, 30 Apr 2008, Zhu Yi wrote:
>
> > On Tue, 2008-04-29 at 09:27 -0400, John W. Linville wrote:
> > >
> > > > Do we have a way to make "select IWLWIFI" generate CONFIG_IWLWIFI
> > > with
> > > > the same state as CONFIG_IWLCORE (or CONFIG_IWL3945)? AFAICS,
> > > > CONFIG_IWLWIFI is always 'y' whenever CONFIG_IWLCORE is 'y' or 'm'.
> > > If
> > > > the latter is 'm', the Makefile will generate a empty built-in.o
> > > which
> > > > requires vmlinux to update unnecessarily every time we only compile
> > > > iwl3945/4965 modules.
> > >
> > > Can you do something like "default IWLCORE'? Untested, off the top
> > > of my head...
> >
> > I just realized the kernel now updates vmlinux when I type 'make' even
> > if nothing is changed in the source code. Is this a bug or feature?
>
> I see files in arch/x86/kernel/acpi/realmode/ always being built.
> Is that what you see or is it something else?
>
> You can do
> make V=2 all >build.log 2>&1
> to see what is being rebuilt and hopefully why.
> Then post that and maybe we can fix it (with the right people helping).
I found below fixes the problem. Sam, could you take a look?
Thanks,
-yi
diff --git a/Makefile b/Makefile
index 39516bf..7788c77 100644
--- a/Makefile
+++ b/Makefile
@@ -812,7 +812,7 @@ endif
# build vmlinux.o first to catch section mismatch errors early
ifdef CONFIG_KALLSYMS
-.tmp_vmlinux1: vmlinux.o
+#.tmp_vmlinux1: vmlinux.o
endif
vmlinux.o: $(vmlinux-lds) $(vmlinux-init) $(vmlinux-main) FORCE
$(call if_changed_rule,vmlinux-modpost)
next prev parent reply other threads:[~2008-04-30 9:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 22:27 [PATCH] Allow building iwl3945 without iwl4965 Jason Riedy
2008-04-27 22:43 ` David Miller
2008-04-29 2:19 ` Zhu Yi
2008-04-29 13:27 ` John W. Linville
2008-04-30 2:14 ` Zhu Yi
2008-04-30 2:17 ` David Miller
2008-04-30 2:31 ` Zhu Yi
2008-04-30 2:32 ` David Miller
2008-04-30 4:46 ` Bill Fink
2008-04-30 2:36 ` Randy.Dunlap
2008-04-30 9:34 ` Zhu Yi [this message]
2008-05-02 15:07 ` Sam Ravnborg
2008-05-04 1:50 ` Zhu Yi
2008-05-05 18:25 ` [2.6 patch] make IWLWIFI a tristate Adrian Bunk
2008-05-05 19:40 ` David Miller
2008-05-05 19:42 ` Adrian Bunk
2008-05-06 1:26 ` Zhu Yi
2008-05-06 7:05 ` David Miller
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=1209548066.2827.42.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=davem@davemloft.net \
--cc=jason@acm.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sam@ravnborg.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).