From: David Miller <davem@davemloft.net>
To: chardin@2wire.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pfkey: sending an SADB_GET responds with an SADB_GET
Date: Wed, 17 Oct 2007 19:29:06 -0700 (PDT) [thread overview]
Message-ID: <20071017.192906.112623207.davem@davemloft.net> (raw)
In-Reply-To: <C33BCE5A.25D04%chardin@2wire.com>
From: Charles Hardin <chardin@2wire.com>
Date: Wed, 17 Oct 2007 14:36:10 -0700
> Kernel needs to respond to an SADB_GET with the same message type to conform
> to the RFC 2367 Section 3.1.5
I can't apply this:
1) We need you to provide an appropriate Signed-off-by: line
in the changelog of your patch.
2) Your email client corrupted the patch, changing tabs into spaces,
and adding newline breaks to long lines.
Please resubmit with these two errors corrected, thank you.
prev parent reply other threads:[~2007-10-18 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 21:36 [PATCH] pfkey: sending an SADB_GET responds with an SADB_GET Charles Hardin
2007-10-18 2:29 ` 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=20071017.192906.112623207.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chardin@2wire.com \
--cc=linux-kernel@vger.kernel.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).