From: Christoph Schulz <develop@kristov•de>
To: Daniel Borkmann <dborkman@redhat•com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
linux-ppp@vger•kernel.org, paulus@samba•org, isdn@linux-pingi•de
Subject: Re: [PATCH net-next] net: ppp: don't call sk_chk_filter twice
Date: Sun, 13 Jul 2014 15:06:34 +0200 [thread overview]
Message-ID: <53C2845A.3080009@kristov.de> (raw)
In-Reply-To: <53C25EF9.7030909@redhat.com>
Hello!
Am 13.07.2014 12:27, schrieb Daniel Borkmann:
> I think the patch makes sense, and you could submit it against net tree
> (so 'PATCH net' in subject) with a slightly different commit log at the
> beginning, but the rest could stay explaining that that's the case for
> 3.15. By that, this could then be picked up into the net tree and thus
> Dave can queue it for stable inclusion. If you need any help, let me know.
I have just resubmitted the patch and hope I did it better this time.
Please let me know whether the commit log is correct now.
Thank you,
Christoph Schulz
prev parent reply other threads:[~2014-07-13 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 7:10 [PATCH net-next] net: ppp: don't call sk_chk_filter twice Christoph Schulz
2014-07-12 3:59 ` Alexei Starovoitov
2014-07-12 10:23 ` Daniel Borkmann
2014-07-12 13:49 ` [PATCH net-next] net: filter: sk_chk_filter() no longer mangles filter Eric Dumazet
2014-07-12 15:23 ` Daniel Borkmann
2014-07-13 1:29 ` Alexei Starovoitov
2014-07-14 6:28 ` David Miller
2014-07-12 21:11 ` [PATCH net-next] net: ppp: don't call sk_chk_filter twice Christoph Schulz
2014-07-13 1:44 ` Alexei Starovoitov
2014-07-13 7:03 ` Christoph Schulz
2014-07-13 10:27 ` Daniel Borkmann
2014-07-13 13:06 ` Christoph Schulz [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=53C2845A.3080009@kristov.de \
--to=develop@kristov$(echo .)de \
--cc=alexei.starovoitov@gmail$(echo .)com \
--cc=dborkman@redhat$(echo .)com \
--cc=isdn@linux-pingi$(echo .)de \
--cc=linux-ppp@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paulus@samba$(echo .)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