From: Michal Schmidt <mschmidt@redhat.com>
To: "Vlad Zolotarov" <vladz@broadcom.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Dmitry Kravkov" <dmitry@broadcom.com>,
"Eilon Greenstein" <eilong@broadcom.com>,
"mirqus@gmail.com" <mirqus@gmail.com>
Subject: Re: [PATCH 1/3] bnx2x: remove TPA_ENABLE_FLAG
Date: Wed, 31 Aug 2011 17:58:49 +0200 [thread overview]
Message-ID: <20110831175849.328192b8@alice> (raw)
In-Reply-To: <201108311816.30468.vladz@broadcom.com>
On Wed, 31 Aug 2011 18:16:30 +0300 Vlad Zolotarov wrote:
> On Wednesday 31 August 2011 18:00:34 Michal Schmidt wrote:
> > if (bnx2x_reload) {
> > - if (bp->recovery_state == BNX2X_RECOVERY_DONE)
> > + if (bp->recovery_state == BNX2X_RECOVERY_DONE) {
> > + /*
> > + * Cheat! Normally dev->features will be
> > set after we
> > + * return, but that's too late. We need to
> > know how to
> > + * configure the NIC when reloading it, so
> > update
> > + * the features early.
> > + */
> > + dev->features = features;
> > return bnx2x_reload_if_running(dev);
>
> NACK
>
> This is bogus - what if bnx2x_reload_if_running(dev)
> (bnx2x_nic_load()) failes? The original dev->features would be
> lost...
Well, yes, but since the NIC would be now not working, do we really
care about its features? :-)
Michal
next prev parent reply other threads:[~2011-08-31 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 15:00 [PATCH 0/3 net-next] bnx2x: VLAN stripping toggle and a small cleanup Michal Schmidt
2011-08-31 15:00 ` [PATCH 1/3] bnx2x: remove TPA_ENABLE_FLAG Michal Schmidt
2011-08-31 15:16 ` Vlad Zolotarov
2011-08-31 15:58 ` Michal Schmidt [this message]
2011-08-31 16:13 ` Vladislav Zolotarov
2011-08-31 18:05 ` Michał Mirosław
2011-09-01 8:37 ` Vladislav Zolotarov
2011-09-01 9:37 ` Michał Mirosław
2011-09-01 10:52 ` Vladislav Zolotarov
2011-08-31 16:55 ` Michal Schmidt
2011-08-31 15:00 ` [PATCH 2/3] bnx2x: do not set NETIF_F_LRO in bnx2x_init_bp Michal Schmidt
2011-08-31 15:00 ` [PATCH 3/3] bnx2x: expose HW RX VLAN stripping toggle Michal Schmidt
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=20110831175849.328192b8@alice \
--to=mschmidt@redhat.com \
--cc=dmitry@broadcom.com \
--cc=eilong@broadcom.com \
--cc=mirqus@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vladz@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