From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: netdev@vger.kernel.org, linux-sh@vger.kernel.org,
ben.dooks@codethink.co.uk
Subject: Re: [PATCH] micrel: fix masking off LED bits
Date: Tue, 18 Mar 2014 23:27:41 +0000 [thread overview]
Message-ID: <1643301.laIYkMizQV@avalon> (raw)
In-Reply-To: <201403190258.16812.sergei.shtylyov@cogentembedded.com>
Hi Sergei,
Thank you for the patch.
On Wednesday 19 March 2014 02:58:16 Sergei Shtylyov wrote:
> Commit 20d8435a1cff (phy: micrel: add of configuration for LED mode) made
> the obvious mistake when masking off the LED mode bits: forgot to do a
> logical NOT to the mask with which it ANDs the register value, so that
> unrelated bits are cleared instead.
>
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Good catch.
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> This patch is against DaveM's 'net-next.git' repo.
>
> drivers/net/phy/micrel.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: net-next/drivers/net/phy/micrel.c
> =================================> --- net-next.orig/drivers/net/phy/micrel.c
> +++ net-next/drivers/net/phy/micrel.c
> @@ -167,7 +167,7 @@ static int kszphy_setup_led(struct phy_d
> if (temp < 0)
> return temp;
>
> - temp &= 3 << shift;
> + temp &= ~(3 << shift);
> temp |= val << shift;
> rc = phy_write(phydev, reg, temp);
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-03-18 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 22:58 [PATCH] micrel: fix masking off LED bits Sergei Shtylyov
2014-03-18 23:27 ` Laurent Pinchart [this message]
2014-03-19 8:12 ` Ben Dooks
2014-03-19 16:21 ` Florian Fainelli
2014-03-19 18:35 ` Sergei Shtylyov
2014-03-19 21:42 ` David Miller
2014-03-20 17:44 ` Sergei Shtylyov
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=1643301.laIYkMizQV@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
/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).