From: David Miller <davem@davemloft.net>
To: christophe.leroy@c-s.fr
Cc: pantelis.antoniou@gmail.com, vbordug@ru.mvista.com,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: fs_enet: do not call phy_stop() in interrupts
Date: Wed, 17 Jan 2018 15:44:45 -0500 (EST) [thread overview]
Message-ID: <20180117.154445.283511690122382070.davem@davemloft.net> (raw)
In-Reply-To: <20180116093305.A04A26EEC5@localhost.localdomain>
From: Christophe Leroy <christophe.leroy@c-s.fr>
Date: Tue, 16 Jan 2018 10:33:05 +0100 (CET)
> In case of TX timeout, fs_timeout() calls phy_stop(), which
> triggers the following BUG_ON() as we are in interrupt.
...
> This patch moves fs_timeout() actions into an async worker.
>
> Fixes: commit 48257c4f168e5 ("Add fs_enet ethernet network driver, for several embedded platforms")
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
Applied, thank you.
prev parent reply other threads:[~2018-01-17 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 9:33 [PATCH] net: fs_enet: do not call phy_stop() in interrupts Christophe Leroy
2018-01-17 20:44 ` 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=20180117.154445.283511690122382070.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=pantelis.antoniou@gmail.com \
--cc=vbordug@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).