From: Andreas Mohr <andi@lisas.de>
To: David Miller <davem@davemloft.net>
Cc: zambrano@broadcom.com, dave@thedillows.org, mb@bu3sch.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] b44.c box lockup fix (netconsole): ratelimit NAPI poll error message
Date: Mon, 30 Nov 2009 13:17:44 +0100 [thread overview]
Message-ID: <20091130121744.GA28479@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <20091130.001541.134590904.davem@davemloft.net>
Hi,
now managed to see the replies, thanks for the notification Michael!
(I'm afraid our SMTP trap won't get lifted since it's probably
justified given the SPAM situation).
> The patch below is what I'll check in to fix this, thanks.
Seems fine.
> I'll queue this b44 patch up for -stable too.
Dito.
Thank you very much,
Andreas Mohr
prev parent reply other threads:[~2009-11-30 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 21:35 [PATCH] b44.c box lockup fix (netconsole): ratelimit NAPI poll error message Andreas Mohr
2009-11-25 22:56 ` David Miller
2009-11-30 8:15 ` David Miller
2009-11-30 8:16 ` David Miller
2009-11-30 12:17 ` Andreas Mohr [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=20091130121744.GA28479@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=dave@thedillows.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=zambrano@broadcom.com \
/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