netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Alexander Duyck <alexander.h.duyck@redhat.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH v2] fm10k: Report MAC address on driver load
Date: Fri, 19 Jun 2015 02:15:56 -0700	[thread overview]
Message-ID: <1434705356.3530.82.camel@intel.com> (raw)
In-Reply-To: <20150619023812.1345.75383.stgit@ahduyck-vm-fedora22>

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

On Thu, 2015-06-18 at 19:41 -0700, Alexander Duyck wrote:
> This change adds the MAC address to the list of values recorded on
> driver
> load.  The MAC address represents the serial number of the unit and
> allows
> us to track the value should a card be replaced in a system.
> 
> The log message should now be similar in output to that of ixgbe.
> 
> Signed-off-by: Alexander Duyck <alexander.h.duyck@redhat.com>
> ---
> 
> v2: Moved printing of MAC onto separate line similar to ixgbe.
> 
> (Hopefully this works for you Jeff.  I took at look at the patch and
> just
>  moved the bit I needed down.  I figured since this block hasn't
> changed I
>  should be able to get away with just doing this instead of pulling
> and
>  rebasing off of your tree. )
> 
>  drivers/net/ethernet/intel/fm10k/fm10k_pci.c |    3 +++
>  1 file changed, 3 insertions(+)

Works for me!  I have added your updated patch to my queue.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-06-19  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  2:41 [PATCH v2] fm10k: Report MAC address on driver load Alexander Duyck
2015-06-19  9:15 ` Jeff Kirsher [this message]
2015-09-02  2:01 ` [Intel-wired-lan] " Singh, Krishneil K

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=1434705356.3530.82.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=alexander.h.duyck@redhat.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --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).