From: David Miller <davem@davemloft.net>
To: inguin@gmx.de
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
rmk+kernel@armlinux.org.uk, andrew@lunn.ch, f.fainelli@gmail.com
Subject: Re: [PATCH] net: phy: fix wrong mask to phy_modify()
Date: Mon, 12 Feb 2018 11:47:47 -0500 (EST) [thread overview]
Message-ID: <20180212.114747.1883056426847767210.davem@davemloft.net> (raw)
In-Reply-To: <20180212110252.27804-1-inguin@gmx.de>
From: Ingo van Lil <inguin@gmx.de>
Date: Mon, 12 Feb 2018 12:02:52 +0100
> When forcing a specific link mode, the PHY driver must clear the
> existing speed and duplex bits in BMCR while preserving some other
> control bits. This logic was accidentally inverted with the introduction
> of phy_modify().
>
> Signed-off-by: Ingo van Lil <inguin@gmx.de>
Applied and queued up for -stable.
prev parent reply other threads:[~2018-02-12 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 11:02 [PATCH] net: phy: fix wrong mask to phy_modify() Ingo van Lil
2018-02-12 13:39 ` Andrew Lunn
2018-02-12 16:47 ` David Miller [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=20180212.114747.1883056426847767210.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=inguin@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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).