From: Andrew Lunn <andrew@lunn.ch>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: phy: fix two issues with linkmode bitmaps
Date: Sun, 25 Nov 2018 21:47:53 +0100 [thread overview]
Message-ID: <20181125204753.GG18663@lunn.ch> (raw)
In-Reply-To: <3917cdd2-ae04-7392-4b08-cf2d15082dcd@gmail.com>
> Eventually we'd have three types of mii_xxx_to_linkmode_yyy functions:
>
> 1. Function first zeroes the destination linkmode bitmap
> 2. Function sets bits in the linkmode bitmap but doesn't clear bits
> if condition isn't met
> 3. Function clears / sets bits it's responsible for
>
> example case 1: mmd_eee_adv_to_linkmode
> example case 2: mii_stat1000_to_linkmode_lpa_t
> example case 3: what you just proposed as fix for
> mii_adv_to_linkmode_adv_t
>
> Because function naming is the same I'm afraid they easily can be used
> incorrectly (the bugs we just discuss are good examples). Maybe it
> could be an option to reflect the semantics in the name like this
> (better suited proposals welcome):
>
> case 1: mii_xxx_to_linkmode_yyy
> case 2: mii_xxx_or_linkmode_yyy
> case 3: mii_xxx_mod_linkmode_yyy
Hi Heiner
That is a good idea. We should probably do this first, it will help
find the bugs.
Andrew
next prev parent reply other threads:[~2018-11-26 7:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 14:23 [PATCH net-next] net: phy: fix two issues with linkmode bitmaps Heiner Kallweit
2018-11-25 16:45 ` Andrew Lunn
2018-11-25 17:21 ` Heiner Kallweit
2018-11-25 20:47 ` Andrew Lunn [this message]
2018-11-26 2:10 ` Andrew Lunn
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=20181125204753.GG18663@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@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).