From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Andrew Lunn <andrew@lunn.ch>, David Miller <davem@davemloft.net>
Cc: Vivien Didelot <vivien.didelot@gmail.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net] net: dsa: mv88e6xxx: Fix serdes irq setup going recursive
Date: Mon, 28 Jan 2019 11:37:41 +0300 [thread overview]
Message-ID: <a9530fd9-0f69-5025-28f3-a671a9fe23ac@cogentembedded.com> (raw)
In-Reply-To: <20190127214800.4202-1-andrew@lunn.ch>
Hello!
On 28.01.2019 0:48, Andrew Lunn wrote:
> Duec to a typo, mv88e6390_serdes_irq_setup() calls itself, rather than
Due?
> mv88e6390x_serdes_irq_setup(). It then blows the stack, and shortly
> after the machine blows up.
Never seen a stack overflow in the kernel... :-)
> Fixes: 2defda1f4b91 ("net: dsa: mv88e6xxx: Add support for SERDES on ports 2-8 for 6390X")
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
MBR, Sergei
prev parent reply other threads:[~2019-01-28 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-27 21:48 [PATCH net] net: dsa: mv88e6xxx: Fix serdes irq setup going recursive Andrew Lunn
2019-01-28 7:20 ` David Miller
2019-01-28 8:37 ` Sergei Shtylyov [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=a9530fd9-0f69-5025-28f3-a671a9fe23ac@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.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