From: Daniel Borkmann <daniel@iogearbox•net>
To: Andrzej Hajda <a.hajda@samsung•com>,
Jamal Hadi Salim <jhs@mojatatu•com>,
"David S. Miller" <davem@davemloft•net>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung•com>,
Marek Szyprowski <m.szyprowski@samsung•com>,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: [PATCH 26/31] net/sched: use kmemdup rather than duplicating its implementation
Date: Fri, 07 Aug 2015 12:35:32 +0200 [thread overview]
Message-ID: <55C489F4.9090104@iogearbox.net> (raw)
In-Reply-To: <1438934377-4922-27-git-send-email-a.hajda@samsung.com>
On 08/07/2015 09:59 AM, Andrzej Hajda wrote:
> The patch was generated using fixed coccinelle semantic patch
> scripts/coccinelle/api/memdup.cocci [1].
>
> [1]: http://permalink.gmane.org/gmane.linux.kernel/2014320
>
> Signed-off-by: Andrzej Hajda <a.hajda@samsung•com>
Acked-by: Daniel Borkmann <daniel@iogearbox•net>
Not sure where the rest of this series went, but if you want this patch
to be routed via net-next tree (which I recommend, to avoid cross tree
conflicts), then you would need to send these patches separately, rebased
to that tree, and also mention [PATCH net-next XX/YY] in the subject.
^^^^^^^^
Thanks,
Daniel
next prev parent reply other threads:[~2015-08-07 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1438934377-4922-1-git-send-email-a.hajda@samsung.com>
2015-08-07 7:59 ` [PATCH 16/31] net/cavium/liquidio: use kmemdup rather than duplicating its implementation Andrzej Hajda
2015-09-16 10:02 ` Andrzej Hajda
2015-08-07 7:59 ` [PATCH 26/31] net/sched: " Andrzej Hajda
2015-08-07 10:35 ` Daniel Borkmann [this message]
2015-08-07 7:59 ` [PATCH 27/31] net/tipc: " Andrzej Hajda
2015-09-16 10:07 ` Andrzej Hajda
2015-09-17 9:58 ` Jon Maloy
2015-09-17 1:19 ` Ying Xue
2015-08-07 7:59 ` [PATCH 28/31] net/xfrm: " Andrzej Hajda
2015-08-12 10:25 ` Steffen Klassert
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=55C489F4.9090104@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=a.hajda@samsung$(echo .)com \
--cc=b.zolnierkie@samsung$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=jhs@mojatatu$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=m.szyprowski@samsung$(echo .)com \
--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