All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH S60 1/1] i40e: rename auto_disable_flags to hw_disabled_flags
Date: Thu, 02 Feb 2017 02:18:26 -0800	[thread overview]
Message-ID: <1486030706.2409.14.camel@intel.com> (raw)
In-Reply-To: <1486016013-11773-1-git-send-email-bimmy.pujari@intel.com>

On Wed, 2017-02-01 at 22:13 -0800, Bimmy Pujari wrote:
> From: Harshitha Ramamurthy <harshitha.ramamurthy@intel.com>
> 
> A previous commit introduced a field that tracks the features
> that are disabled due to HW resource limitations as opposed
> to the featured disabled by the user. This patch changes the
> name of the field to make it more readable since it might get
> confusing when looking at code containing both the flags
> field and the auto_disable_features field together.
> 
> Signed-off-by: Harshitha Ramamurthy <harshitha.ramamurthy@intel.com>
> Change-ID: Idcc9888659698f6fe3ccff17c8c3f09b5026f708
> ---
> ?drivers/net/ethernet/intel/i40e/i40e.h???????? |? 8 ++++++--
> ?drivers/net/ethernet/intel/i40e/i40e_ethtool.c | 10 ++++-----
> ?drivers/net/ethernet/intel/i40e/i40e_main.c??? | 28 +++++++++++++-------
> ------
> ?drivers/net/ethernet/intel/i40e/i40e_txrx.c??? | 20 +++++++++---------
> ?4 files changed, 35 insertions(+), 31 deletions(-)

This does not apply cleanly at all, so I am dropping this patch.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20170202/0561dda6/attachment.asc>

  reply	other threads:[~2017-02-02 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02  6:13 [Intel-wired-lan] [next PATCH S60 1/1] i40e: rename auto_disable_flags to hw_disabled_flags Bimmy Pujari
2017-02-02 10:18 ` Jeff Kirsher [this message]
2017-02-03 18:00   ` Pujari, Bimmy

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=1486030706.2409.14.camel@intel.com \
    --to=jeffrey.t.kirsher@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.