From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: 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,
Miles Lane <miles.lane@gmail.com>
Subject: ACPI_DOCK bug: noone cares
Date: Sun, 9 Jul 2006 02:06:01 +0200 [thread overview]
Message-ID: <20060709000601.GA13938@stusta.de> (raw)
In-Reply-To: <20060625204039.GG23314@stusta.de>
On Sun, Jun 25, 2006 at 10:40:39PM +0200, Adrian Bunk wrote:
> On Sun, Jun 25, 2006 at 01:13:04PM -0700, Miles Lane 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.
>
> I'm often trying to reproduce compile errors, and it's always a pain in
> the ass when I have to construct a complete .config based on such a
> fragment instead of simply using the complete .config of the reporter.
>
> And people for whom a few kB would matter wouldn't subscribe to
> linux-kernel...
>
> > Yes, that's right. It is compiled as a module. So this just needs
> > a tweaked config rule, right?
>
> It would be a solution to let HOTPLUG_PCI_ACPI depend on
> (ACPI_DOCK || ACPI_DOCK=n), or the #if in
> include/acpi/acpi_drivers.h could be changed to
> #if defined(CONFIG_ACPI_DOCK) || (defined(CONFIG_ACPI_DOCK_MODULE) && defined(MODULE))
>
> Which one suits better the intention is better is a question Kristen has
> to answer.
Two weeks ago, we had:
- a bug report
- a detailed description how to possibly fix this issue
What we did NOT have was:
- any reaction by the patch author or any maintainer
(although with the exception of Linus, the recipients of the problem
description were exactly the same as the ones in this email)
A few days later, the patch that includes this bug was included in
Linus' tree.
Two weeks later, the bug is still present in both latest -mm and Linus'
tree.
Linus, please do a
git-revert a5e1b94008f2a96abf4a0c0371a55a56b320c13e
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-07-09 0:06 UTC|newest]
Thread overview: 15+ 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 ` Adrian Bunk [this message]
2006-07-09 16:01 ` ACPI_DOCK bug: noone cares Linus Torvalds
2006-06-26 5: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' Keith Owens
2006-06-26 6:22 ` Keith Owens
2006-06-26 22:15 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2006-07-09 19:59 ACPI_DOCK bug: noone cares Brown, Len
2006-07-09 22:05 ` Linus Torvalds
2006-07-09 20:01 Brown, Len
2006-07-09 22:24 Brown, Len
2006-07-09 22:38 ` Linus Torvalds
2006-07-09 23:15 ` Nigel Cunningham
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=20060709000601.GA13938@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--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 \
--cc=torvalds@osdl.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