netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mahesh Bandewar <maheshb@google.com>
To: "Michał Mirosław" <mirqus@gmail.com>
Cc: Matt Carlson <mcarlson@broadcom.com>,
	David Miller <davem@davemloft.net>,
	linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 1/2] tg3: Fix NETIF_F_LOOPBACK error
Date: Fri, 20 May 2011 10:56:34 -0700	[thread overview]
Message-ID: <BANLkTimUz4eTqcdV4-v2cH6qE0vcRnUXPA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikO2kW2FBcyjwNuk30B58nbsj9vdQ@mail.gmail.com>

On Thu, May 19, 2011 at 11:57 PM, Michał Mirosław <mirqus@gmail.com> wrote:
> 2011/5/20 Matt Carlson <mcarlson@broadcom.com>:
>> On Thu, May 19, 2011 at 06:15:18PM -0700, Mahesh Bandewar wrote:
>>> On Thu, May 19, 2011 at 6:11 PM, Matt Carlson <mcarlson@broadcom.com> wrote:
>>> > Mahesh Bandewar noticed that the features cleanup in commit
>>> > 0da0606f493c5cdab74bdcc96b12f4305ad94085, entitled
>>> > "tg3: Consolidate all netdev feature assignments", mistakenly sets
>>> > NETIF_F_LOOPBACK by default. ?This patch corrects the error.
>>> >
>>> > Signed-off-by: Matt Carlson <mcarlson@broadcom.com>
>>> > ---
>>> > ?drivers/net/tg3.c | ? ?3 ++-
>>> > ?1 files changed, 2 insertions(+), 1 deletions(-)
>>> >
>>> > diff --git a/drivers/net/tg3.c b/drivers/net/tg3.c
>>> > index 012ce70..0b78c5d 100644
>>> > --- a/drivers/net/tg3.c
>>> > +++ b/drivers/net/tg3.c
>>> > @@ -15080,6 +15080,8 @@ static int __devinit tg3_init_one(struct pci_dev *pdev,
>>> > ? ? ? ? ? ? ? ? ? ? ? ?features |= NETIF_F_TSO_ECN;
>>> > ? ? ? ?}
>>> >
>>> > + ? ? ? dev->features |= features;
>>> > +
>>> > ? ? ? ?/*
>>> > ? ? ? ? * Add loopback capability only for a subset of devices that support
>>> > ? ? ? ? * MAC-LOOPBACK. Eventually this need to be enhanced to allow INT-PHY
>>> > @@ -15090,7 +15092,6 @@ static int __devinit tg3_init_one(struct pci_dev *pdev,
>>> > ? ? ? ? ? ? ? ?/* Add the loopback capability */
>>> > ? ? ? ? ? ? ? ?features |= NETIF_F_LOOPBACK;
>>> >
>>> > - ? ? ? dev->features |= features;
>>> > ? ? ? ?dev->hw_features |= features;
>>> > ? ? ? ?dev->vlan_features |= features;
>>> I think this line should go up too. Otherwise newly created vlan
>>> device(s) will have spurious loopback bit set.
>> Yes.  You are right.  I thought vlan_features functioned like
>> hw_features.
>
> Probably NETIF_F_LOOPBACK should be forcibly set on VLAN devices when
> underlying device has it enabled. Just a quick thought for discussion.
>
I think that's a good idea for the sake of correctness and should be
done when we enable / disable loopback.

--mahesh..

> Best Regards,
> Michał Mirosław
>

      reply	other threads:[~2011-05-20 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20  1:11 [PATCH net-next 1/2] tg3: Fix NETIF_F_LOOPBACK error Matt Carlson
2011-05-20  1:15 ` Mahesh Bandewar
2011-05-20  1:59   ` Matt Carlson
2011-05-20  6:57     ` Michał Mirosław
2011-05-20 17:56       ` Mahesh Bandewar [this message]

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=BANLkTimUz4eTqcdV4-v2cH6qE0vcRnUXPA@mail.gmail.com \
    --to=maheshb@google.com \
    --cc=davem@davemloft.net \
    --cc=mcarlson@broadcom.com \
    --cc=mirqus@gmail.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).