From: Keith Owens <kaos@ocs.com.au>
To: "Miles Lane" <miles.lane@gmail.com>
Cc: "Adrian Bunk" <bunk@stusta.de>,
"Kristen Accardi" <kristen.c.accardi@intel.com>,
"Dave Hansen" <haveblue@us.ibm.com>,
"Andrew Morton" <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
gregkh@suse.de, len.brown@intel.com, linux-acpi@vger.kernel.org
Subject: Re: 2.6.17-mm2 -- drivers/built-in.o: In function `is_pci_dock_device':acpiphp_glue.c:(.text+0x12364): undefined reference to `is_dock_device'
Date: Mon, 26 Jun 2006 15:56:49 +1000 [thread overview]
Message-ID: <13783.1151301409@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 25 Jun 2006 13:13:04 MST." <a44ae5cd0606251313n5e7654f3t652df65e811325b5@mail.gmail.com>
"Miles Lane" (on Sun, 25 Jun 2006 13:13:04 -0700) wrote:
>Should I attach my entire .config file in the future? It's large enough that
>I try to trim it to avoid bloating people's inboxes.
Mail the result of
sed -ne 's/^CONFIG_//p' .config
That is typically less than 40% of the full .config size, and it can be
fully regenerated by
yes '' | make oldconfig
next prev parent reply other threads:[~2006-06-26 5:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 19:56 2.6.17-mm2 -- drivers/built-in.o: In function `is_pci_dock_device':acpiphp_glue.c:(.text+0x12364): undefined reference to `is_dock_device' Miles Lane
2006-06-25 20:09 ` Adrian Bunk
2006-06-25 20:13 ` Miles Lane
2006-06-25 20:40 ` Adrian Bunk
2006-07-09 0:06 ` ACPI_DOCK bug: noone cares Adrian Bunk
2006-07-09 16:01 ` Linus Torvalds
2006-06-26 5:56 ` Keith Owens [this message]
2006-06-26 6:22 ` 2.6.17-mm2 -- drivers/built-in.o: In function `is_pci_dock_device':acpiphp_glue.c:(.text+0x12364): undefined reference to `is_dock_device' Keith Owens
2006-06-26 22:15 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2006-07-09 23:03 Brown, Len
2006-07-09 23:12 ` Adrian Bunk
2006-07-10 1:46 ` Linus Torvalds
2006-07-09 23:06 Brown, Len
2006-07-10 2:02 Brown, Len
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=13783.1151301409@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=gregkh@suse.de \
--cc=haveblue@us.ibm.com \
--cc=kristen.c.accardi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.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