From: David Miller <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: johannes@sipsolutions.net, netdev@vger.kernel.org
Subject: Re: sungem triggers NAPI warning
Date: Sat, 23 Feb 2008 19:58:27 -0800 (PST) [thread overview]
Message-ID: <20080223.195827.227137243.davem@davemloft.net> (raw)
In-Reply-To: <1203634227.10422.200.camel@pasglop>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Fri, 22 Feb 2008 09:50:27 +1100
> I still think the change is obviously correct, so I'll give a second
> close look at the code and produce a patch.
Patch coming soon? :)
next prev parent reply other threads:[~2008-02-24 3:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 21:38 sungem triggers NAPI warning Johannes Berg
2008-02-21 2:54 ` Benjamin Herrenschmidt
2008-02-21 13:05 ` Johannes Berg
2008-02-21 22:50 ` Benjamin Herrenschmidt
2008-02-24 3:58 ` David Miller [this message]
2008-02-24 4:43 ` Benjamin Herrenschmidt
2008-03-23 10:35 ` David Miller
2008-03-23 12:07 ` Benjamin Herrenschmidt
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=20080223.195827.227137243.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--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 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).