From: Benjamin LaHaise <bcrl@kvack.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH ipv4 multicast] Fix IPv4 multicast over network namespaces
Date: Tue, 27 Mar 2012 20:49:54 -0400 [thread overview]
Message-ID: <20120328004954.GC2367@kvack.org> (raw)
In-Reply-To: <20120327.173541.1721499825104013533.davem@davemloft.net>
On Tue, Mar 27, 2012 at 05:35:41PM -0400, David Miller wrote:
> No signoff.
My apologies. Doing this manually clearly isn't working, so I've switched
to a script to try to catch this.
> No proper subsystem prefix in Subject line (should be "ipv4: " here)
I'm trying to get this right, and it looks like I botched this again, for
that I am truely sorry.
-ben
> And third you've been warned about this repeatedly in your previous
> patch postings.
>
> Therefore I'm not applying this.
--
"Thought is the essence of where you are now."
prev parent reply other threads:[~2012-03-28 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 16:12 [PATCH ipv4 multicast] Fix IPv4 multicast over network namespaces Benjamin LaHaise
2012-03-27 21:35 ` David Miller
2012-03-28 0:49 ` Benjamin LaHaise [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=20120328004954.GC2367@kvack.org \
--to=bcrl@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).