linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: balbi@ti.com
Cc: joe@perches.com, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org, wimax@linuxwimax.org,
	linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com,
	linux-s390@vger.kernel.org, johannes@sipsolutions.net,
	uclinux-dist-devel@blackfin.uclinux.org,
	linux-kernel@vger.kernel.org, linux-c6x-dev@linux-c6x.org,
	linux-mips@linux-mips.org,
	user-mode-linux-devel@lists.sourceforge.net,
	user-mode-linux-user@lists.sourceforge.net,
	e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH net-next 0/8] etherdevice: Rename random_ether_addr to eth_random_addr
Date: Mon, 16 Jul 2012 03:29:01 -0700 (PDT)	[thread overview]
Message-ID: <20120716.032901.1657058688119342783.davem@davemloft.net> (raw)
In-Reply-To: <20120716101437.GC22638@arwen.pp.htv.fi>

From: Felipe Balbi <balbi@ti.com>
Date: Mon, 16 Jul 2012 13:14:38 +0300

> if you're really renaming the function, then this patch alone will break
> all of the below users. That should all be a single patch, I'm afraid.

It would help if you actually read his patches before saying what they
might or might not do.

He provides a macro in the first patch that provides the old name,
and this will get removed at the end.

  reply	other threads:[~2012-07-16 10:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 10:16 [PATCH] etherdevice: introduce broadcast_ether_addr Johannes Berg
2012-07-03 15:13 ` Joe Perches
2012-07-03 15:16   ` Johannes Berg
2012-07-09  6:58 ` David Miller
2012-07-10 16:18   ` [PATCH] etherdevice: introduce eth_broadcast_addr Johannes Berg
2012-07-11  0:09     ` Paul Gortmaker
2012-07-11  0:41       ` David Miller
2012-07-11  1:09         ` Joe Perches
2012-07-13  5:33           ` [PATCH net-next 0/8] etherdevice: Rename random_ether_addr to eth_random_addr Joe Perches
2012-07-13  5:33             ` [PATCH net-next 4/8] wireless: Use eth_random_addr Joe Perches
2012-07-13  5:54               ` Hin-Tak Leung
2012-07-13  7:15               ` Gertjan van Wingerde
2012-07-16 10:14             ` [PATCH net-next 0/8] etherdevice: Rename random_ether_addr to eth_random_addr Felipe Balbi
2012-07-16 10:29               ` David Miller [this message]
2012-07-16 11:12                 ` Felipe Balbi
2012-07-16 11:17                   ` David Miller
2012-07-17  5:39             ` David Miller
2012-07-11  7:27       ` [PATCH] etherdevice: introduce eth_broadcast_addr Johannes Berg
2012-07-11  1:07     ` David Miller

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=20120716.032901.1657058688119342783.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=balbi@ti.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=joe@perches.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-c6x-dev@linux-c6x.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    --cc=users@rt2x00.serialmonkey.com \
    --cc=wimax@linuxwimax.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).