From: David Miller <davem@davemloft.net>
To: florian@openwrt.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/2 net-next-2.6] r6040: fix multicast operations
Date: Wed, 23 Feb 2011 14:35:58 -0800 (PST) [thread overview]
Message-ID: <20110223.143558.102556959.davem@davemloft.net> (raw)
In-Reply-To: <201102232332.40712.florian@openwrt.org>
From: Florian Fainelli <florian@openwrt.org>
Date: Wed, 23 Feb 2011 23:32:40 +0100
> It is appropriate for kernel versions including e1d44477 (net: convert
> multiple drivers to use netdev_for_each_mc_addr). The patch was generated from
> a net-next-2.6 tree, thus the mention in the subject, which was certainly
> misleading, sorry about that.
There is no disconnect between those two things, what tree a patch
applies cleanly against and what tree it is meant to be applied to.
They are always equal.
There is therefore no confusion, and it was not misleading.
prev parent reply other threads:[~2011-02-23 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 14:32 [PATCH 1/2 net-next-2.6] r6040: fix multicast operations Florian Fainelli
2011-02-23 22:22 ` David Miller
2011-02-23 22:32 ` Florian Fainelli
2011-02-23 22:35 ` 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=20110223.143558.102556959.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=florian@openwrt.org \
--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;
as well as URLs for NNTP newsgroup(s).