From: David Miller <davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, philipl@overt.org, hmh@hmh.eng.br,
linville@tuxdriver.com
Subject: Re: [GIT]: Networking for 2.6.28
Date: Sat, 11 Oct 2008 15:04:56 -0700 (PDT) [thread overview]
Message-ID: <20081011.150456.193701531.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0810111303510.3402@nehalem.linux-foundation.org>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat, 11 Oct 2008 13:10:52 -0700 (PDT)
> On Sat, 11 Oct 2008, David Miller wrote:
> > This patch should fix that case, let me know if it works:
>
> How about you test it?
Yep, indeed I did give it a try.
> It wasn't my bug-report, I just reported another
> report from somebody who _does_ run randconfig.
Where did you see this? I wouldn't have asked all of these idiotic
questions if I had a link to the report. Then I could go grab the
config used to produce the problem and then ping the reporter with
a test patch. :-)
> Here's another one:
>
> drivers/built-in.o: In function `bt_poll_rfkill':
> toshiba_acpi.c:(.text+0x37346): undefined reference to `input_event'
>
> where the cause seems to be a totally broken Kconfig entry ACPI_TOSHIBA.
Where are these reports coming from? Some automated randconfig thing
that gets posted somewhere? I'd really like to look at this stuff, it
seems very useful.
> You can't just do
>
> select INPUT_POLLDEV
>
> since that in turn needs all the _other_ input stuff. Yes, yes, things
> like various keyboard drivers do exactly that, but they are already inside
> "if INPUT_KEYBOARD/INPUT_MISC" or similar.
>
> So at the very least, you'd now have to have it do a "depends on INPUT" or
> something like that.
>
> Or perhaps just make that particular _feature_ depend on it, rather than
> make the whole driver depend on or select it.
Do you want me to fix this ACPI build failure in the networking tree?
I'm more than happy to :-)
prev parent reply other threads:[~2008-10-11 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 21:49 [GIT]: Networking for 2.6.28 David Miller
2008-10-11 16:43 ` Linus Torvalds
2008-10-11 16:46 ` Linus Torvalds
2008-10-11 16:48 ` Patrick McHardy
2008-10-11 17:57 ` Linus Torvalds
2008-10-11 18:12 ` David Miller
2008-10-11 19:19 ` David Miller
2008-10-11 20:10 ` Linus Torvalds
2008-10-11 22:04 ` David Miller [this message]
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=20081011.150456.193701531.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=philipl@overt.org \
--cc=torvalds@linux-foundation.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).