netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mirq-linux@rere.qmqm.pl
Cc: netdev@vger.kernel.org, vladz@broadcom.com, eilong@broadcom.com
Subject: Re: [PATCH v5] net: bnx2x: convert to hw_features
Date: Tue, 12 Apr 2011 14:52:53 -0700 (PDT)	[thread overview]
Message-ID: <20110412.145253.28813257.davem@davemloft.net> (raw)
In-Reply-To: <20110412193823.0823213A65@rere.qmqm.pl>

From: Michał Mirosław <mirq-linux@rere.qmqm.pl>
Date: Tue, 12 Apr 2011 21:38:23 +0200 (CEST)

> Since ndo_fix_features callback is postponing features change when
> bp->recovery_state != BNX2X_RECOVERY_DONE, netdev_update_features()
> has to be called again when this condition changes. Previously,
> ethtool_ops->set_flags callback returned -EBUSY in that case
> (it's not possible in the new model).
> 
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> 
> v5: - don't delay set_features, as it's rtnl_locked - same as recovery process
> v4: - complete bp->rx_csum -> NETIF_F_RXCSUM conversion
>     - add check for failed ndo_set_features in ndo_open callback
> v3: - include NETIF_F_LRO in hw_features
>     - don't call netdev_update_features() if bnx2x_nic_load() failed
> v2: - comment in ndo_fix_features callback

I've applied this.

From what I can tell the is basic agreement from the Broadcom folks,
and if any fixups are needed that can be done with follow-up
patches.

Thanks.

  reply	other threads:[~2011-04-12 21:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10 14:47 [PATCH] net: bnx2x: convert to hw_features Michał Mirosław
2011-04-10 15:10 ` Vladislav Zolotarov
2011-04-10 15:23   ` Michał Mirosław
2011-04-10 15:35   ` [PATCH v2] " Michał Mirosław
2011-04-11 14:10     ` Vladislav Zolotarov
2011-04-11 19:54       ` [PATCH v3] " Michał Mirosław
2011-04-11 20:26         ` [PATCH v4] " Michał Mirosław
2011-04-12 12:10           ` Vladislav Zolotarov
2011-04-12 14:07             ` Michał Mirosław
2011-04-12 14:36               ` Vladislav Zolotarov
2011-04-12 14:49                 ` Michał Mirosław
2011-04-13  9:36                   ` Vladislav Zolotarov
2011-04-12 19:38                 ` [PATCH v5] " Michał Mirosław
2011-04-12 21:52                   ` David Miller [this message]
2011-04-21 14:52                   ` Eric Dumazet
2011-04-21 18:49                     ` Vladislav Zolotarov
2011-04-21 19:19                       ` Ben Hutchings
2011-04-21 22:15                         ` Michał Mirosław
2011-04-21 22:52                           ` Ben Hutchings
2011-04-21 23:14                             ` Michał Mirosław
2011-04-21 23:44                             ` Michał Mirosław
2011-04-21 23:12                         ` [PATCH] net: fix hw_features ethtool_ops->set_flags compatibility Michał Mirosław
2011-04-21 23:19                         ` [PATCH v2] " Michał Mirosław
2011-04-21 23:21                         ` [PATCH v3] " Michał Mirosław
2011-04-21 23:59                         ` [PATCH v4] " Michał Mirosław
2011-04-22  0:21                           ` David Miller
2011-04-22  5:16                           ` Eric Dumazet
2011-04-22  5:27                             ` Eric Dumazet
2011-04-21 22:41                     ` [PATCH v5] net: bnx2x: convert to hw_features Michał Mirosław
2011-04-22  4:51                       ` Eric Dumazet
2011-04-21 22:42                     ` [PATCH] net: make WARN_ON in dev_disable_lro() useful Michał Mirosław
2011-04-22  5:11                       ` Eric Dumazet
2011-04-25 18:56                         ` David Miller
2011-04-11 20:12       ` [PATCH v2] net: bnx2x: convert to hw_features Michał Mirosław
2011-04-12  7:26         ` Vladislav Zolotarov
2011-04-12  7:46           ` Vladislav Zolotarov

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=20110412.145253.28813257.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eilong@broadcom.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --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;
as well as URLs for NNTP newsgroup(s).