From: David Miller <davem@davemloft.net>
To: claudiu.manoil@freescale.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] gianfar: Fix P1010 config regression (SQ polling)
Date: Thu, 20 Mar 2014 16:09:44 -0400 (EDT) [thread overview]
Message-ID: <20140320.160944.268619450160968028.davem@davemloft.net> (raw)
In-Reply-To: <1395236379-16116-1-git-send-email-claudiu.manoil@freescale.com>
From: Claudiu Manoil <claudiu.manoil@freescale.com>
Date: Wed, 19 Mar 2014 15:39:39 +0200
> The P1010 device tree restricts the number of
> supported interrupt groups to 1, although the eth
> controller can support 2 interrupt groups and the
> driver assumes the Multi-Group mode ("fsl,etsec2" model).
>
> So, in this case the assumption that the Multi-Group
> mode (MQ_MG_MODE) devices always support 2 interrupt
> groups is false. To fix this, a check for the actual
> number of interrupt groups enabled in the board's
> device tree has been added in gfar_probe for the
> "fsl,etsec2" devices.
>
> Without this fix, P1010 based boards claim support for
> 2 Tx queues to the net stack but only one is actually
> allocated, leading to NULL access in xmit. This issue
> was introduced by enabling Single-Queue polling for
> the P1010 devices.
>
> Signed-off-by: Claudiu Manoil <claudiu.manoil@freescale.com>
Please repost this, referencing the specific commit that introduced
the regression. Either inline in the commit message, or using
the standard "Fixes: " tag right before your signoff.
Thank you.
next prev parent reply other threads:[~2014-03-20 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 13:39 [PATCH net-next] gianfar: Fix P1010 config regression (SQ polling) Claudiu Manoil
2014-03-20 20:09 ` David Miller [this message]
2014-03-21 7:33 ` [PATCH net-next v2] " Claudiu Manoil
2014-03-24 4:41 ` David Miller
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=20140320.160944.268619450160968028.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=claudiu.manoil@freescale.com \
--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).