netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: kumaran.4353@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net] Remove unnecessary condition check in phy
Date: Mon, 07 Apr 2014 21:15:37 -0400 (EDT)	[thread overview]
Message-ID: <20140407.211537.2275013635206463873.davem@davemloft.net> (raw)
In-Reply-To: <CAGVrzcbeFpd+7xgxPNVUW-TEVEeP+wh+XvVkgwvnQBJk7OqHCw@mail.gmail.com>

From: Florian Fainelli <f.fainelli@gmail.com>
Date: Mon, 7 Apr 2014 18:09:00 -0700

> 2014-04-07 11:58 GMT-07:00 David Miller <davem@davemloft.net>:
>> From: Balakumaran Kannan <kumaran.4353@gmail.com>
>> Date: Sat, 05 Apr 2014 13:00:16 +0530
>>
>>> This condition check makes no difference in the code flow since 3.10
>>>
>>> Signed-off-by: Balakumaran Kannan <kumaran.4353@gmail.com>
>>
>> The big questions is, was this intentional?
> 
> It was before a33e6112d9b0 ("phy: Elimination the forced speed
> reduction algorithm") because the PHY having PHY_HAS_MAGICANEG set
> would not go through the PHY speed reduction algorithm. Now, this is
> useless as there is a subsequent break and no conditional code based
> on PHY_HAS_MAGICANEG (which means that we should also kill its usage
> at some point).

Yep, I read through the history and that's why I noticed the patch didn't
apply, I was about to apply it :-)

> Feel free to add my reviewed-by tag after fixing the mangling David spotted.
> 
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>

Will do, thanks Florian.

  reply	other threads:[~2014-04-08  1:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05  7:30 [PATCH net] Remove unnecessary condition check in phy Balakumaran Kannan
2014-04-07 18:58 ` David Miller
2014-04-08  1:09   ` Florian Fainelli
2014-04-08  1:15     ` David Miller [this message]
2014-04-08  0: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=20140407.211537.2275013635206463873.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kumaran.4353@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).