From: Sven Van Asbroeck <thesven73@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Sven Van Asbroeck <svendev@arcx.com>,
siva.kallam@broadcom.com, prashant@broadcom.com,
mchan@broadcom.com, David Miller <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] tg3: optionally get mac address from devicetree
Date: Sat, 17 Nov 2018 10:58:12 -0500 [thread overview]
Message-ID: <CAGngYiVLw6sGGTijReKR2zcfZcAXnuY9KJaVm1Lm19_hgzh49g@mail.gmail.com> (raw)
In-Reply-To: <20181115200018.GC32274@lunn.ch>
Please this cancel this patch. As suggested by Dave Miller, it has
been replaced by:
[PATCH v1] tg3: optionally use eth_platform_get_mac_address() to get mac address
prev parent reply other threads:[~2018-11-17 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 13:52 [PATCH v2] tg3: optionally get mac address from devicetree thesven73
2018-11-15 20:00 ` Andrew Lunn
2018-11-17 15:58 ` Sven Van Asbroeck [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=CAGngYiVLw6sGGTijReKR2zcfZcAXnuY9KJaVm1Lm19_hgzh49g@mail.gmail.com \
--to=thesven73@gmail.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=prashant@broadcom.com \
--cc=siva.kallam@broadcom.com \
--cc=svendev@arcx.com \
/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).