From: Andrew Lunn <andrew@lunn.ch>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next] igb: allow setting MAC address on i211 using a device tree blob V2
Date: Tue, 16 Feb 2016 23:47:25 +0100 [thread overview]
Message-ID: <20160216224725.GC6033@lunn.ch> (raw)
In-Reply-To: <255BB17A-515B-467A-8ED6-96F1173D233E@gmail.com>
> I can supply some kind of usage description/example, showing how to
> use this feature to pull in the MAC address from u-boot and route it
> to the i210. Just uncertain as how to name the respective
> file. igb.txt or i210.txt come to mind. Do you prefer one over the
> other?
Hi John
It is quite common to name it after the compatible string, so
intel,i210.txt
Thanks
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: John Holland <jotihojr@gmail.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [next] igb: allow setting MAC address on i211 using a device tree blob V2
Date: Tue, 16 Feb 2016 23:47:25 +0100 [thread overview]
Message-ID: <20160216224725.GC6033@lunn.ch> (raw)
In-Reply-To: <255BB17A-515B-467A-8ED6-96F1173D233E@gmail.com>
> I can supply some kind of usage description/example, showing how to
> use this feature to pull in the MAC address from u-boot and route it
> to the i210. Just uncertain as how to name the respective
> file. igb.txt or i210.txt come to mind. Do you prefer one over the
> other?
Hi John
It is quite common to name it after the compatible string, so
intel,i210.txt
Thanks
Andrew
next prev parent reply other threads:[~2016-02-16 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 22:04 [Intel-wired-lan] [next] igb: allow setting MAC address on i211 using a device tree blob V2 John Holland
2016-02-13 22:04 ` John Holland
2016-02-16 16:58 ` Andrew Lunn
2016-02-16 16:58 ` Andrew Lunn
2016-02-16 22:34 ` John Holland
2016-02-16 22:34 ` John Holland
2016-02-16 22:47 ` Andrew Lunn [this message]
2016-02-16 22:47 ` Andrew Lunn
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=20160216224725.GC6033@lunn.ch \
--to=andrew@lunn.ch \
--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.