From: David Miller <davem@davemloft.net>
To: stigge@antcom.de
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kevin.wells@nxp.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] net: lpc_eth: Fix rename of dev_hw_addr_random
Date: Sun, 01 Apr 2012 16:17:14 -0400 (EDT) [thread overview]
Message-ID: <20120401.161714.1988118567020406881.davem@davemloft.net> (raw)
In-Reply-To: <1332974186-12962-1-git-send-email-stigge@antcom.de>
From: Roland Stigge <stigge@antcom.de>
Date: Thu, 29 Mar 2012 00:36:26 +0200
> In parallel to the integration of lpc_eth.c, dev_hw_addr_random() has been
> renamed to eth_hw_addr_random(). This patch fixes it also in the new driver
> lpc_eth.c.
>
> Signed-off-by: Roland Stigge <stigge@antcom.de>
Applied and queued up for -stable.
prev parent reply other threads:[~2012-04-01 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 22:36 [PATCH] net: lpc_eth: Fix rename of dev_hw_addr_random Roland Stigge
2012-04-01 20:17 ` David Miller [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=20120401.161714.1988118567020406881.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kevin.wells@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stigge@antcom.de \
/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).