[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180810124029.4d2c6c1f@redhat.com>
Date: Fri, 10 Aug 2018 12:40:29 +0200
From: Jesper Dangaard Brouer <brouer@...hat.com>
To: Carlos Neira <cneirabustos@...il.com>
Cc: netdev@...r.kernel.org, ebiederm@...ssion.com,
quentin.monnet@...ronome.com, ys114321@...il.com,
brouer@...hat.com, Daniel Borkmann <borkmann@...earbox.net>
Subject: Re: [PATCH bpf-next] BPF: helpers: New helper to obtain namespace
data from current task
On Thu, 9 Aug 2018 12:07:00 -0400
Carlos Neira <cneirabustos@...il.com> wrote:
> Jesper,
> Here is the updated patch.
>
> From 92633f6819423093932e8d04aa3dc99a5913f6fd Mon Sep 17 00:00:00 2001
> From: Carlos Neira <cneirabustos@...il.com>
> Date: Thu, 9 Aug 2018 09:55:32 -0400
> Subject: [PATCH bpf-next] BPF: helpers: New helper to obtain namespace
> data from current task
>
[...]
Hi Carlos,
This is not how you resubmit a patch, it is both documented in [1] and
[2], that: "In case the patch or patch series has to be reworked and
sent out again in a second or later revision, it is also required to
add a version number (v2, v3, ...) into the subject prefix"
[1] https://github.com/torvalds/linux/blob/master/Documentation/bpf/bpf_devel_QA.rst#q-how-do-i-indicate-which-tree-bpf-vs-bpf-next-my-patch-should-be-applied-to
[2] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#the-canonical-patch-format
Take a look at [1], which toplevel doc is about "HOWTO interact with
BPF subsystem".
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
Powered by blists - more mailing lists