From: David Miller <davem@davemloft.net>
To: linus.luessing@web.de
Cc: b.a.t.m.a.n@lists.open-mesh.org, herbert@gondor.apana.org.au,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, stephen@networkplumber.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv3 net-next 0/4] bridge: multicast snooping patches / exports
Date: Thu, 05 Jun 2014 14:50:59 -0700 (PDT) [thread overview]
Message-ID: <20140605.145059.8146842085083371.davem@davemloft.net> (raw)
In-Reply-To: <20140605212016.GE2544@Linus-Debian>
From: Linus Lüssing <linus.luessing@web.de>
Date: Thu, 5 Jun 2014 23:20:16 +0200
> Oh, I'm sorry, I thought it'd only be necessary for the v1
> patchset. Going to change that from now on. Anyways, here it is
> (copied 'n' pasted):
When I ask for changes, you need to make a new fresh submission
of your patch(s).
prev parent reply other threads:[~2014-06-05 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 18:07 [B.A.T.M.A.N.] [PATCHv3 net-next 1/4] bridge: rename struct bridge_mcast_query/querier Linus Lüssing
2014-06-02 18:07 ` [B.A.T.M.A.N.] [PATCHv3 net-next 2/4] bridge: adhere to querier election mechanism specified by RFCs Linus Lüssing
2014-06-02 18:07 ` [B.A.T.M.A.N.] [PATCHv3 net-next 3/4] bridge: add export of multicast database adjacent to net_dev Linus Lüssing
2014-06-02 18:07 ` [B.A.T.M.A.N.] [PATCHv3 net-next 4/4] bridge: memorize and export selected IGMP/MLD querier port Linus Lüssing
2014-06-02 18:42 ` [B.A.T.M.A.N.] [PATCHv3 net-next 0/4] bridge: multicast snooping patches / exports Linus Lüssing
2014-06-05 7:43 ` David Miller
2014-06-05 21:20 ` Linus Lüssing
2014-06-05 21:50 ` 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=20140605.145059.8146842085083371.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bridge@lists.linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linus.luessing@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).