From: Andrew Lunn <andrew@lunn•ch>
To: Michael Zhivich <mzhivich@akamai•com>
Cc: davem@davemloft•net, siva.kallam@broadcom•com,
prashant@broadcom•com, mchan@broadcom•com, shshaikh@marvell•com,
manishc@marvell•com, netdev@vger•kernel.org
Subject: Re: [PATCH v2 0/3] ethtool: fix use of SPEED_UNKNOWN constant
Date: Mon, 8 Apr 2019 19:54:43 +0200 [thread overview]
Message-ID: <20190408175443.GG15267@lunn.ch> (raw)
In-Reply-To: <1554734927-15522-1-git-send-email-mzhivich@akamai.com>
On Mon, Apr 08, 2019 at 10:48:44AM -0400, Michael Zhivich wrote:
> This patch series addresses 2 related issues:
>
> 1. ethtool_validate_speed() triggers a "signed-unsigned comparison"
> warning due to type difference of SPEED_UNKNOWN constant (int)
> and argument to ethtool_validate_speed (__u32).
>
> 2. some drivers use u16 storage for SPEED_UNKNOWN constant,
> resulting in value truncation and thus failure to test against
> SPEED_UNKNOWN correctly.
>
> This revised series addresses several feedback comments:
> - split up the patch in to series
> - do not unnecessarily change drivers that use "int" storage
> for speed values
Hi Michael
Your v1 had some changes which changed plain int value speeds to using
the SPEED_X macros. Those changes appear to of disappeared. You could
submit them as well.
Thanks
Andrew
next prev parent reply other threads:[~2019-04-08 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 14:48 [PATCH v2 0/3] ethtool: fix use of SPEED_UNKNOWN constant Michael Zhivich
2019-04-08 14:48 ` [PATCH v2 1/3] ethtool: avoid signed-unsigned comparison in ethtool_validate_speed() Michael Zhivich
2019-04-08 14:48 ` [PATCH v2 2/3] broadcom: tg3: fix use of SPEED_UNKNOWN ethtool constant Michael Zhivich
2019-04-08 17:52 ` Andrew Lunn
2019-04-08 14:48 ` [PATCH v2 3/3] qlogic: qlcnic: " Michael Zhivich
2019-04-08 17:53 ` Andrew Lunn
2019-04-08 17:54 ` Andrew Lunn [this message]
2019-04-08 18:40 ` [PATCH v2 0/3] ethtool: fix use of SPEED_UNKNOWN constant Zhivich, Michael
2019-04-08 23:30 ` 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=20190408175443.GG15267@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=manishc@marvell$(echo .)com \
--cc=mchan@broadcom$(echo .)com \
--cc=mzhivich@akamai$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=prashant@broadcom$(echo .)com \
--cc=shshaikh@marvell$(echo .)com \
--cc=siva.kallam@broadcom$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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