From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: linville@tuxdriver.com, tomas.winkler@intel.com,
linux-kernel@vger.kernel.org, kaber@trash.net,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
mabbas@linux.intel.com, ischram@telenet.be, rjw@sisk.pl,
ivdoorn@gmail.com
Subject: Re: [build bug] drivers/built-in.o: In function `rt2x00leds_resume': : undefined reference to `led_classdev_resume'
Date: Sun, 20 Apr 2008 01:54:04 -0700 (PDT) [thread overview]
Message-ID: <20080420.015404.86827224.davem@davemloft.net> (raw)
In-Reply-To: <20080420081302.GA11954@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Sun, 20 Apr 2008 10:13:02 +0200
> Really, your practice of removing networking commits and pull
> requests from lkml does not result in a stellar quality track
> record.
Ingo I started posting them the way you asked me to today.
Because everyone must do as Ingo says or else he'll berate
them on the list every day.
So please, just drop it already. You got what you wanted.
FWIW, all of the patches in question were posted to netdev and
linux-wireless. And I already explained my original logic for not
posting the huge networking merge pull request, it's too damn large
(128K or so) to be useful at all and will result in tons of bounces
(which I have to process btw)
But even with all that, I'm doing it now Ingo, just to make you quiet.
So just LEAVE ME ALONE already!
next prev parent reply other threads:[~2008-04-20 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 8:13 [build bug] drivers/built-in.o: In function `rt2x00leds_resume': : undefined reference to `led_classdev_resume' Ingo Molnar
2008-04-20 8:54 ` David Miller [this message]
2008-04-20 9:05 ` David Miller
2008-04-20 9:31 ` Ivo van Doorn
2008-04-20 9:47 ` David Miller
2008-04-20 10:01 ` David Miller
2008-04-25 7:35 ` Ingo Molnar
2008-04-25 7:39 ` David Miller
2008-04-25 8:00 ` Ingo Molnar
2008-04-25 8: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=20080420.015404.86827224.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=ischram@telenet.be \
--cc=ivdoorn@gmail.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mabbas@linux.intel.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tomas.winkler@intel.com \
--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).