From: Johannes Berg <johannes@sipsolutions•net>
To: David Miller <davem@davemloft•net>
Cc: Julian Anastasov <ja@ssi•bg>,
linux-wireless@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: [PATCH v3 1/4] ipv4: add option to drop unicast encapsulated in L2 multicast
Date: Thu, 28 Jan 2016 13:33:33 +0100 [thread overview]
Message-ID: <1453984413.2217.13.camel@sipsolutions.net> (raw)
In-Reply-To: <1446712923-9136-1-git-send-email-johannes@sipsolutions.net> (sfid-20151105_094304_292739_0426127F)
Hi,
Is there anything I should do about these patches?
I see you marked them as "deferred" in patchwork, but I don't really
know how you're using that state.
johannes
next prev parent reply other threads:[~2016-01-28 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 8:42 [PATCH v3 1/4] ipv4: add option to drop unicast encapsulated in L2 multicast Johannes Berg
2015-11-05 8:42 ` [PATCH v3 2/4] ipv4: add option to drop gratuitous ARP packets Johannes Berg
[not found] ` <1446712923-9136-1-git-send-email-johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2015-11-05 8:42 ` [PATCH v3 3/4] ipv6: add option to drop unicast encapsulated in L2 multicast Johannes Berg
2015-11-05 8:42 ` [PATCH v3 4/4] ipv6: add option to drop unsolicited neighbor advertisements Johannes Berg
2015-11-05 9:09 ` [PATCH v3 1/4] ipv4: add option to drop unicast encapsulated in L2 multicast Julian Anastasov
2016-01-28 12:33 ` Johannes Berg [this message]
[not found] ` <1453984413.2217.13.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2016-01-29 0:16 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2016-02-04 12:31 Johannes Berg
2016-02-11 9:27 ` 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=1453984413.2217.13.camel@sipsolutions.net \
--to=johannes@sipsolutions$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=ja@ssi$(echo .)bg \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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