netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH] net: phy: sfp: correct store of detected link modes
Date: Thu, 29 Nov 2018 13:14:27 +0000	[thread overview]
Message-ID: <20181129131427.GV30658@n2100.armlinux.org.uk> (raw)
In-Reply-To: <87o9a86p6q.fsf@tkos.co.il>

On Thu, Nov 29, 2018 at 02:30:53PM +0200, Baruch Siach wrote:
> Hi Russell,
> 
> Russell King - ARM Linux writes:
> > On Thu, Nov 29, 2018 at 12:40:11PM +0200, Baruch Siach wrote:
> >> The link modes that sfp_parse_support() detects are stored in the
> >> 'modes' bitmap. There is no reason to make an exception for 1000Base-PX
> >> or 1000Base-BX10.
> >
> > I think you may be carrying some local patch, have an incorrect merge,
> > or maybe there's a patch in -next which changed this.
> >
> > Mainline has:
> >
> >         if (bitmap_empty(modes, __ETHTOOL_LINK_MODE_MASK_NBITS)) {
> >                 /* If the encoding and bit rate allows 1000baseX */
> >                 if (id->base.encoding == SFP_ENCODING_8B10B && br_nom &&
> >                     br_min <= 1300 && br_max >= 1200)
> >                         phylink_set(modes, 1000baseX_Full);
> >         }
> >
> > but your patch changes that phylink_set() from:
> >
> >                         phylink_set(support, 1000baseX_Full);
> >
> > to:
> >
> >                         phylink_set(modes, 1000baseX_Full);
> >
> > which in the context of what's in mainline doesn't make sense.
> 
> The code that this patch touches is at line 165 in current mainline as
> of commit 60b548237fe:
> 
>     162         /* 1000Base-PX or 1000Base-BX10 */
>     163         if ((id->base.e_base_px || id->base.e_base_bx10) &&
>     164             br_min <= 1300 && br_max >= 1200)
>     165                 phylink_set(support, 1000baseX_Full);
> 
> net-next as of e561bb29b6 carries no change in this file, as far as I
> can see.

Ah, sorry, I was looking further down.  Yes, your change is correct -
it was missed in 03145864bd0fcac29e33442f39d67d4f28b0777c, so it needs
a fixes tag for that commit.  Probably missed by having patches hanging
around for soo long.

Fixes: 03145864bd0f ("sfp: support 1G BiDi (eg, FiberStore SFP-GE-BX) modules")
Acked-by: Russell King <rmk+kernel@armlinux.org.uk>

Thanks!

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

  reply	other threads:[~2018-11-30  0:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 10:40 [PATCH] net: phy: sfp: correct store of detected link modes Baruch Siach
2018-11-29 10:46 ` Russell King - ARM Linux
2018-11-29 12:30   ` Baruch Siach
2018-11-29 13:14     ` Russell King - ARM Linux [this message]
2018-11-29 18:49 ` 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=20181129131427.GV30658@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=andrew@lunn.ch \
    --cc=baruch@tkos.co.il \
    --cc=f.fainelli@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).