Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [net-next PATCH v2 02/10] intel: Update drivers to use ethtool_sprintf
Date: Wed, 17 Mar 2021 09:36:24 -0700	[thread overview]
Message-ID: <20210317093624.00005020@intel.com> (raw)
In-Reply-To: <161594104491.5644.18446437902161792108.stgit@localhost.localdomain>

Alexander Duyck wrote:

> From: Alexander Duyck <alexanderduyck@fb.com>
> 
> Update the Intel drivers to make use of ethtool_sprintf. The general idea
> is to reduce code size and overhead by replacing the repeated pattern of
> string printf statements and ETH_STRING_LEN counter increments.
> 
> Signed-off-by: Alexander Duyck <alexanderduyck@fb.com>

Thanks!

Acked-by: Jesse Brandeburg <jesse.brandeburg@intel.com>

  reply	other threads:[~2021-03-17 16:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  0:30 [Intel-wired-lan] [net-next PATCH v2 00/10] ethtool: Factor out common code related to writing ethtool strings Alexander Duyck
2021-03-17  0:30 ` [Intel-wired-lan] [net-next PATCH v2 01/10] ethtool: Add common function for filling out strings Alexander Duyck
2021-03-17  0:30 ` [Intel-wired-lan] [net-next PATCH v2 02/10] intel: Update drivers to use ethtool_sprintf Alexander Duyck
2021-03-17 16:36   ` Jesse Brandeburg [this message]
2021-03-17  0:30 ` [Intel-wired-lan] [net-next PATCH v2 03/10] nfp: Replace nfp_pr_et with ethtool_sprintf Alexander Duyck
2021-03-17  0:31 ` [Intel-wired-lan] [net-next PATCH v2 04/10] hisilicon: Update drivers to use ethtool_sprintf Alexander Duyck
2021-03-17  0:31 ` [Intel-wired-lan] [net-next PATCH v2 05/10] ena: Update driver " Alexander Duyck
2021-03-17  0:31 ` [Intel-wired-lan] [net-next PATCH v2 06/10] netvsc: " Alexander Duyck
2021-03-17  0:31 ` [Intel-wired-lan] [net-next PATCH v2 07/10] virtio_net: " Alexander Duyck
2021-03-17  0:31 ` [Intel-wired-lan] [net-next PATCH v2 08/10] vmxnet3: " Alexander Duyck
2021-03-17  0:31 ` [Intel-wired-lan] [net-next PATCH v2 09/10] bna: " Alexander Duyck
2021-03-17  0:31 ` [Intel-wired-lan] [net-next PATCH v2 10/10] ionic: " Alexander Duyck
2021-03-17 16:41 ` [Intel-wired-lan] [net-next PATCH v2 00/10] ethtool: Factor out common code related to writing ethtool strings Jesse Brandeburg
2021-03-17 18:50 ` patchwork-bot+netdevbpf

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=20210317093624.00005020@intel.com \
    --to=jesse.brandeburg@intel.com \
    --cc=intel-wired-lan@osuosl.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