From: Jeff Garzik <jeff@garzik.org>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org, mingo@elte.hu,
aabdulla@nvidia.com
Subject: Re: [patch 20/21] forcedeth: fix locking bug with netconsole
Date: Fri, 28 Mar 2008 18:48:46 -0400 [thread overview]
Message-ID: <47ED75CE.1080400@garzik.org> (raw)
In-Reply-To: <20080328.154353.43255092.davem@davemloft.net>
David Miller wrote:
> From: akpm@linux-foundation.org
> Date: Fri, 28 Mar 2008 14:41:30 -0700
>
>> From: Ingo Molnar <mingo@elte.hu>
>>
>> While using netconsole on forcedeth, lockdep noticed the following locking
>> bug:
>
> Please do not mix device driver changes with core networking
> changes.
FWIW my plan was to snip the net/* stuff and only apply the forcedeth
portion.
(leaving <whomever> to pick up the pieces, should they so desire)
Jeff
next prev parent reply other threads:[~2008-03-28 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 21:41 [patch 20/21] forcedeth: fix locking bug with netconsole akpm
2008-03-28 22:43 ` David Miller
2008-03-28 22:48 ` Jeff Garzik [this message]
2008-03-28 23:42 ` Andrew Morton
2008-03-28 23:46 ` Ingo Molnar
2008-03-29 2:09 ` Jeff Garzik
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=47ED75CE.1080400@garzik.org \
--to=jeff@garzik.org \
--cc=aabdulla@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=mingo@elte.hu \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.