kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Colin King <colin.king@canonical.com>
Cc: davem@davemloft.net, kuba@kernel.org, linux@rempel-privat.de,
	linux-usb@vger.kernel.org, netdev@vger.kernel.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2][next][V2] net: usb: asix: Fix less than zero comparison of a u16
Date: Wed, 09 Jun 2021 22:30:05 +0000	[thread overview]
Message-ID: <162327780599.20375.14960133934732052088.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210609102448.182798-1-colin.king@canonical.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Wed,  9 Jun 2021 11:24:47 +0100 you wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> The comparison of the u16 priv->phy_addr < 0 is always false because
> phy_addr is unsigned. Fix this by assigning the return from the call
> to function asix_read_phy_addr to int ret and using this for the
> less than zero error check comparison.
> 
> [...]

Here is the summary with links:
  - [1/2,next,V2] net: usb: asix: Fix less than zero comparison of a u16
    https://git.kernel.org/netdev/net-next/c/e67665946599
  - [2/2,next,V2] net: usb: asix: ax88772: Fix less than zero comparison of a u16
    https://git.kernel.org/netdev/net-next/c/c6be5a22fde5

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-06-09 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 10:24 [PATCH 1/2][next][V2] net: usb: asix: Fix less than zero comparison of a u16 Colin King
2021-06-09 10:24 ` [PATCH 2/2][next][V2] net: usb: asix: ax88772: " Colin King
2021-06-09 22:30 ` patchwork-bot+netdevbpf [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=162327780599.20375.14960133934732052088.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=colin.king@canonical.com \
    --cc=davem@davemloft.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --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).