From: David Miller <davem@davemloft.net>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org, afleming@freescale.com,
netdev@vger.kernel.org, jgarzik@pobox.com
Subject: Re: [PATCH] gianfar: Fix soft lockup with multi-interrupt TSECs
Date: Mon, 12 Jan 2009 21:57:47 -0800 (PST) [thread overview]
Message-ID: <20090112.215747.18333160.davem@davemloft.net> (raw)
In-Reply-To: <20090112183835.GA25390@oksana.dev.rtsoft.ru>
From: Anton Vorontsov <avorontsov@ru.mvista.com>
Date: Mon, 12 Jan 2009 21:38:35 +0300
> This patch fixes following bug:
>
> BUG: soft lockup - CPU#0 stuck for 61s! [S03mountvirtfs-:922]
...
> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
Applied, thanks Anton.
prev parent reply other threads:[~2009-01-13 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 18:38 [PATCH] gianfar: Fix soft lockup with multi-interrupt TSECs Anton Vorontsov
2009-01-13 5:57 ` David Miller [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=20090112.215747.18333160.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=afleming@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=jgarzik@pobox.com \
--cc=linuxppc-dev@ozlabs.org \
--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).