From: Linus Torvalds <torvalds@linux-foundation.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: Linux 2.6.34-rc3
Date: Sat, 3 Apr 2010 20:39:10 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1004032032160.3634@i5.linux-foundation.org> (raw)
In-Reply-To: <4BB24E5F.3030703@lwfinger.net>
On Tue, 30 Mar 2010, Larry Finger wrote:
>
> I understand that you do not want a whole set of such "fix one such bug at a
> time" patches, but the bottom line is that these lockdep warnings for known
> problems interfere with "normal" debugging because further lockdep checking is
> disabled. I do not feel qualified to detect other cases and fix them. Only when
> a warning hits my logs am I qualified to fix and test.
I'd actually like the owner for this to send me the patches - I don't go
out downloading things from patchwork, and quite frankly, I was expecting
Eric Biederman to follow up on these issues, since that's where the new
requirements came from. Maybe the patches are already waiting in Greg's
tree or something?
But if people are just waiting around for others to take them, if somebody
who has tracked this issue (hint hint, Larry) sends me the final patches,
I can take them that way too.
Linus
next prev parent reply other threads:[~2010-04-04 3:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 19:17 Larry Finger
2010-03-31 2:16 ` Wolfram Sang
2010-03-31 2:40 ` Larry Finger
2010-04-04 3:39 ` Linus Torvalds [this message]
2010-04-04 3:54 ` Wolfram Sang
2010-04-04 4:06 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-03-30 17:50 Linus Torvalds
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=alpine.LFD.2.00.1004032032160.3634@i5.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome