From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: billfink@mindspring.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net: Fix some fallout from the etner_addr_copy() changes.
Date: Wed, 22 Jan 2014 14:56:36 -0800 [thread overview]
Message-ID: <1390431396.31946.95.camel@joe-AO722> (raw)
In-Reply-To: <20140121.225431.117378955801559296.davem@davemloft.net>
On Tue, 2014-01-21 at 22:54 -0800, David Miller wrote:
> From: Bill Fink <billfink@mindspring.com>
> Date: Tue, 21 Jan 2014 23:23:31 -0500
>
> > The commit message indicates problems with appletalk/aarp.c,
> > atm/lec.c, and caif/caif_usb.c, but the diffstat and patch only
> > address the first two and not caif/caif_usb.c. Is that intended
> > or am I missing something.
>
> Thanks for catching that, I just pushed the missing change.
My apologies for my stupid carelessness in the
patches I sent here.
I thought #define ETH_ALEN was in the same #include
as ether_addr_copy and I didn't bother compiling.
prev parent reply other threads:[~2014-01-22 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 3:03 [PATCH] net: Fix some fallout from the etner_addr_copy() changes David Miller
2014-01-22 4:07 ` François-Xavier Le Bail
2014-01-22 4:23 ` Bill Fink
2014-01-22 6:54 ` David Miller
2014-01-22 22:56 ` Joe Perches [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=1390431396.31946.95.camel@joe-AO722 \
--to=joe@perches.com \
--cc=billfink@mindspring.com \
--cc=davem@davemloft.net \
--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