netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michał Mirosław" <mirqus@gmail.com>
To: Mahesh Bandewar <maheshb@google.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 2/9] net-ethtool: Convert (hw_/vlan_/wanted_)features fields from u32 type to u64.
Date: Mon, 25 Apr 2011 10:48:52 +0200	[thread overview]
Message-ID: <BANLkTikjhY-M7ZB8azYctq9p1ORmA8PBKQ@mail.gmail.com> (raw)
In-Reply-To: <1303515367-25595-3-git-send-email-maheshb@google.com>

2011/4/23 Mahesh Bandewar <maheshb@google.com>:
>
> Signed-off-by: Mahesh Bandewar <maheshb@google.com>
> ---
>  include/linux/ethtool.h |   26 +++++++------
>  net/core/ethtool.c      |   89 ++++++++++++++++------------------------------
>  2 files changed, 45 insertions(+), 70 deletions(-)
>
> diff --git a/include/linux/ethtool.h b/include/linux/ethtool.h
> index 9de3127..71e8a02 100644
> --- a/include/linux/ethtool.h
> +++ b/include/linux/ethtool.h
> @@ -605,10 +605,10 @@ struct ethtool_flash {
>  * @never_changed: mask of features not changeable for any device
>  */
>  struct ethtool_get_features_block {
> -       __u32   available;
> -       __u32   requested;
> -       __u32   active;
> -       __u32   never_changed;
> +       __u64   available;
> +       __u64   requested;
> +       __u64   active;
> +       __u64   never_changed;
>  };
[...]

Please don't do it like this. G/SFEATURES were prepared to handle
multiple words when needed. This means that it's enough to just split
the u64 into two u32 sets represented in ethtool_get/set_features.

Best Regards,
Michał Mirosław

      parent reply	other threads:[~2011-04-25  8:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-22 23:35 [PATCH 0/9] Convert features fields from u32 to type u64 Mahesh Bandewar
2011-04-22 23:35 ` [PATCH 1/9] net-dev: Convert (hw_/vlan_/wanted_)features fields from u32 type to u64 Mahesh Bandewar
2011-04-22 23:36   ` [PATCH 2/9] net-ethtool: " Mahesh Bandewar
2011-04-22 23:36     ` [PATCH 3/9] net-core: " Mahesh Bandewar
2011-04-22 23:36       ` [PATCH 4/9] net-tcp: " Mahesh Bandewar
2011-04-22 23:36         ` [PATCH 5/9] net-udp: " Mahesh Bandewar
2011-04-22 23:36           ` [PATCH 6/9] net-vlan: " Mahesh Bandewar
2011-04-22 23:36             ` [PATCH 7/9] net-bridge: " Mahesh Bandewar
2011-04-22 23:36               ` [PATCH 8/9] net-ipv4: " Mahesh Bandewar
2011-04-22 23:36                 ` [PATCH 9/9] net-ipv6: " Mahesh Bandewar
2011-04-24  5:30     ` [PATCH 2/9] net-ethtool: " Ben Hutchings
2011-04-25  5:28       ` David Miller
2011-04-25 18:14       ` Mahesh Bandewar
2011-04-25  8:48     ` Michał Mirosław [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=BANLkTikjhY-M7ZB8azYctq9p1ORmA8PBKQ@mail.gmail.com \
    --to=mirqus@gmail.com \
    --cc=davem@davemloft.net \
    --cc=maheshb@google.com \
    --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).