From: Jesper Dangaard Brouer <brouer@redhat•com>
To: Carlos Neira <cneirabustos@gmail•com>
Cc: netdev@vger•kernel.org, ebiederm@xmission•com,
quentin.monnet@netronome•com, ys114321@gmail•com,
brouer@redhat•com, Daniel Borkmann <borkmann@iogearbox•net>
Subject: Re: [PATCH bpf-next] BPF: helpers: New helper to obtain namespace data from current task
Date: Fri, 10 Aug 2018 12:40:29 +0200 [thread overview]
Message-ID: <20180810124029.4d2c6c1f@redhat.com> (raw)
In-Reply-To: <20180809160700.mrs6gcdcghrxex7z@krondor>
On Thu, 9 Aug 2018 12:07:00 -0400
Carlos Neira <cneirabustos@gmail•com> wrote:
> Jesper,
> Here is the updated patch.
>
> From 92633f6819423093932e8d04aa3dc99a5913f6fd Mon Sep 17 00:00:00 2001
> From: Carlos Neira <cneirabustos@gmail•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
next prev parent reply other threads:[~2018-08-10 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 13:18 [PATCH bpf-next] BPF: helpers: New helper to obtain namespace data from current task Carlos Neira
2018-08-09 13:46 ` Jesper Dangaard Brouer
2018-08-09 14:49 ` Carlos Neira
2018-08-09 16:07 ` Carlos Neira
2018-08-10 10:40 ` Jesper Dangaard Brouer [this message]
2018-08-10 19:08 ` Carlos Neira
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=20180810124029.4d2c6c1f@redhat.com \
--to=brouer@redhat$(echo .)com \
--cc=borkmann@iogearbox$(echo .)net \
--cc=cneirabustos@gmail$(echo .)com \
--cc=ebiederm@xmission$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=quentin.monnet@netronome$(echo .)com \
--cc=ys114321@gmail$(echo .)com \
/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