From: Tom Lendacky <thomas.lendacky@amd.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-kernel@vger.kernel.org
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
linux-renesas-soc@vger.kernel.org, netdev@vger.kernel.org,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 4/4] net: amd-xgbe: fix comparison to bitshift when dealing with a mask
Date: Mon, 5 Feb 2018 16:35:34 -0600 [thread overview]
Message-ID: <048aded0-9b5e-60f5-ec67-a00a4858ffac@amd.com> (raw)
In-Reply-To: <20180205201002.23621-5-wsa+renesas@sang-engineering.com>
On 2/5/2018 2:10 PM, Wolfram Sang wrote:
> Due to a typo, the mask was destroyed by a comparison instead of a bit
> shift.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Excellent find.
Acked-by: Tom Lendacky <thomas.lendacky@amd.com>
David, this should also be applied to the 4.14 and 4.15 stable releases.
Thanks,
Tom
> ---
> Only build tested. To be applied individually per subsystem.
>
> drivers/net/ethernet/amd/xgbe/xgbe-drv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/amd/xgbe/xgbe-drv.c b/drivers/net/ethernet/amd/xgbe/xgbe-drv.c
> index 7a3ebfd236f5eb..100adee778dfd6 100644
> --- a/drivers/net/ethernet/amd/xgbe/xgbe-drv.c
> +++ b/drivers/net/ethernet/amd/xgbe/xgbe-drv.c
> @@ -595,7 +595,7 @@ static void xgbe_isr_task(unsigned long data)
>
> reissue_mask = 1 << 0;
> if (!pdata->per_channel_irq)
> - reissue_mask |= 0xffff < 4;
> + reissue_mask |= 0xffff << 4;
>
> XP_IOWRITE(pdata, XP_INT_REISSUE_EN, reissue_mask);
> }
>
next prev parent reply other threads:[~2018-02-05 22:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 20:09 [PATCH 0/4] tree-wide: fix comparison to bitshift when dealing with a mask Wolfram Sang
2018-02-05 20:09 ` Wolfram Sang
2018-02-05 20:09 ` [PATCH 1/4] v4l: vsp1: fix mask creation for MULT_ALPHA_RATIO Wolfram Sang
2018-02-22 16:07 ` Laurent Pinchart
2018-02-05 20:09 ` [PATCH 2/4] drm/exynos: fix comparison to bitshift when dealing with a mask Wolfram Sang
2018-02-05 20:09 ` Wolfram Sang
2018-02-06 0:06 ` Inki Dae
2018-02-06 0:06 ` Inki Dae
2018-02-05 20:10 ` [PATCH 3/4] v4l: dvb-frontends: stb0899: " Wolfram Sang
2018-02-05 20:10 ` [PATCH 4/4] net: amd-xgbe: " Wolfram Sang
2018-02-05 22:35 ` Tom Lendacky [this message]
2018-02-06 16:25 ` David Miller
2018-02-06 8:20 ` [PATCH 0/4] tree-wide: " Geert Uytterhoeven
2018-02-06 8:20 ` Geert Uytterhoeven
2018-02-06 8:20 ` Geert Uytterhoeven
2018-02-06 8:28 ` Wolfram Sang
2018-02-06 8:28 ` Wolfram Sang
2018-02-06 13:10 ` Dan Carpenter
2018-02-06 13:10 ` Dan Carpenter
2018-02-06 13:10 ` Dan Carpenter
2018-02-06 13:15 ` Julia Lawall
2018-02-06 13:15 ` Julia Lawall
2018-02-06 13:23 ` Dan Carpenter
2018-02-06 13:23 ` Dan Carpenter
2018-02-06 13:40 ` Julia Lawall
2018-02-06 13:40 ` Julia Lawall
2018-02-06 13:53 ` Wolfram Sang
2018-02-06 13:53 ` Wolfram Sang
2018-02-06 13:54 ` Julia Lawall
2018-02-06 13:54 ` Julia Lawall
2018-02-06 13:57 ` Wolfram Sang
2018-02-06 13:57 ` Wolfram Sang
2018-02-06 13:59 ` Dan Carpenter
2018-02-06 13:59 ` Dan Carpenter
2018-02-06 13:59 ` Dan Carpenter
2018-02-06 14:08 ` Julia Lawall
2018-02-06 14:08 ` Julia Lawall
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=048aded0-9b5e-60f5-ec67-a00a4858ffac@amd.com \
--to=thomas.lendacky@amd.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.