From: Dan Carpenter <dan.carpenter@oracle.com>
To: Yuval Mintz <yuvalmin@broadcom.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bnx2x: Added EEE support
Date: Mon, 22 Oct 2012 15:06:47 +0300 [thread overview]
Message-ID: <20121022120647.GC7380@mwanda> (raw)
In-Reply-To: <979A8436335E3744ADCD3A9F2A2B68A5027223@SJEXCHMB10.corp.ad.broadcom.com>
On Sun, Jun 10, 2012 at 07:47:13AM +0000, Yuval Mintz wrote:
> > The patch c8c60d88c59c: "bnx2x: Added EEE support" from Jun 6, 2012,
> > leads to the following warning:
> > drivers/net/ethernet/broadcom/bnx2x/bnx2x_link.c:10121
> > bnx2x_848x3_config_init()
> > error: buffer overflow 'params->req_duplex' 2 <= 4
> >
>
> Hi Dan,
>
> You are right - this is indeed an error, although one that shouldn't
> affect any existing bnx2x chip supporting EEE.
>
> I'll send a patch correcting it soon.
>
What happened with this?
regards,
dan carpenter
next prev parent reply other threads:[~2012-10-22 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 13:09 bnx2x: Added EEE support Dan Carpenter
2012-06-10 7:47 ` Yuval Mintz
2012-10-22 12:06 ` Dan Carpenter [this message]
2012-10-22 12:15 ` Yuval Mintz
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=20121022120647.GC7380@mwanda \
--to=dan.carpenter@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=yuvalmin@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;
as well as URLs for NNTP newsgroup(s).