From: Andrew Lunn <andrew@lunn.ch>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH ethtool v2 1/9] netlink: get rid of signed/unsigned comparison warnings
Date: Sun, 23 Aug 2020 22:06:52 +0200 [thread overview]
Message-ID: <20200823200652.GH2588906@lunn.ch> (raw)
In-Reply-To: <06083ab4701848eeb56afec9a5d8b757dd6cb399.1598210544.git.mkubecek@suse.cz>
On Sun, Aug 23, 2020 at 09:40:18PM +0200, Michal Kubecek wrote:
> Use unsigned types where appropriate to get rid of compiler warnings about
> comparison between signed and unsigned integer values in netlink code.
>
> v2: avoid casts in dump_features()
>
> Signed-off-by: Michal Kubecek <mkubecek@suse.cz>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2020-08-23 20:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 19:40 [PATCH ethtool v2 0/9] compiler warnings cleanup, part 2 Michal Kubecek
2020-08-23 19:40 ` [PATCH ethtool v2 1/9] netlink: get rid of signed/unsigned comparison warnings Michal Kubecek
2020-08-23 20:06 ` Andrew Lunn [this message]
2020-08-23 19:40 ` [PATCH ethtool v2 2/9] ioctl: check presence of eeprom length argument properly Michal Kubecek
2020-08-23 19:40 ` [PATCH ethtool v2 3/9] ioctl: prevent argc underflow in do_perqueue() Michal Kubecek
2020-08-23 19:40 ` [PATCH ethtool v2 4/9] ioctl: make argc counters unsigned Michal Kubecek
2020-08-23 20:08 ` Andrew Lunn
2020-08-23 19:40 ` [PATCH ethtool v2 5/9] ioctl: get rid of signed/unsigned comparison warnings Michal Kubecek
2020-08-23 19:40 ` [PATCH ethtool v2 6/9] get rid of signed/unsigned comparison warnings in register dump parsers Michal Kubecek
2020-08-23 19:40 ` [PATCH ethtool v2 7/9] settings: simplify link_mode_info[] initializers Michal Kubecek
2020-08-23 19:40 ` [PATCH ethtool v2 8/9] ioctl: convert cmdline_info arrays to named initializers Michal Kubecek
2020-08-23 19:40 ` [PATCH ethtool v2 9/9] build: add -Wextra to default CFLAGS Michal Kubecek
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=20200823200652.GH2588906@lunn.ch \
--to=andrew@lunn.ch \
--cc=mkubecek@suse.cz \
--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).