From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Amit Salecha <amit.salecha@qlogic.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Amerigo Wang <amwang@redhat.com>,
Anirban Chakraborty <anirban.chakraborty@qlogic.com>
Subject: Re: [PATCH -next] qlcnic: fail when try to setup unsupported features
Date: Mon, 28 Jun 2010 14:58:19 +0200 [thread overview]
Message-ID: <20100628145819.74d22d5f@dhcp-lab-109.englab.brq.redhat.com> (raw)
In-Reply-To: <99737F4847ED0A48AECC9F4A1974A4B80F82CB7D46@MNEXMB2.qlogic.org>
On Mon, 28 Jun 2010 07:36:04 -0500
Amit Salecha <amit.salecha@qlogic.com> wrote:
> - ethtool_op_set_flags(netdev, data);
> -
> - hw_lro = (data & ETH_FLAG_LRO) ? QLCNIC_LRO_ENABLED : 0;
> + if (data & ETH_FLAG_LRO) {
> + hw_lro = QLCNIC_LRO_ENABLED;
> + netdev->features |= NETIF_F_LRO;
> + } else {
> + hw_lro = 0;
> + netdev->features &= ~NETIF_F_LRO;
> + }
>
> Above hunk is unnecessary.
Yes, I did not describe that change in the changelog. I want to
remove such usage of ethtool_op_set_flags() for my furher patches, where
I plan to add return EOPNOTSUPP to ethtool_op_set_flags().
Stanislaw
next prev parent reply other threads:[~2010-06-28 12:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 9:31 [PATCH -next] qlcnic: fail when try to setup unsupported features Stanislaw Gruszka
2010-06-28 12:36 ` Amit Salecha
2010-06-28 12:58 ` Stanislaw Gruszka [this message]
2010-06-28 13:09 ` Amit Salecha
2010-06-28 14:14 ` Stanislaw Gruszka
2010-06-28 14:18 ` Ben Hutchings
2010-06-29 14:41 ` Ben Hutchings
2010-06-29 15:00 ` Stanislaw Gruszka
2010-06-29 15:05 ` Ben Hutchings
2010-06-29 16:01 ` [RFC] [PATCH] ethtool: Change ethtool_op_set_flags to validate flags Ben Hutchings
2010-06-30 5:26 ` Jeff Garzik
2010-06-30 11:21 ` Stanislaw Gruszka
2010-06-30 20:47 ` David Miller
2010-06-29 16:59 ` [PATCH -next] qlcnic: fail when try to setup unsupported features David Miller
2010-06-28 13:16 ` Ben Hutchings
2010-06-28 13:30 ` Ben Hutchings
2010-06-28 14:18 ` Stanislaw Gruszka
2010-06-29 7:55 ` 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=20100628145819.74d22d5f@dhcp-lab-109.englab.brq.redhat.com \
--to=sgruszka@redhat.com \
--cc=amit.salecha@qlogic.com \
--cc=amwang@redhat.com \
--cc=anirban.chakraborty@qlogic.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).