From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesper Dangaard Brouer 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 Message-ID: <20180810124029.4d2c6c1f@redhat.com> References: <20180809131800.11338-1-cneirabustos@gmail.com> <20180809154653.40396ce3@redhat.com> <20180809160700.mrs6gcdcghrxex7z@krondor> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, ebiederm@xmission.com, quentin.monnet@netronome.com, ys114321@gmail.com, brouer@redhat.com, Daniel Borkmann To: Carlos Neira Return-path: Received: from mx3-rdu2.redhat.com ([66.187.233.73]:50014 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727335AbeHJNJw (ORCPT ); Fri, 10 Aug 2018 09:09:52 -0400 In-Reply-To: <20180809160700.mrs6gcdcghrxex7z@krondor> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, 9 Aug 2018 12:07:00 -0400 Carlos Neira wrote: > Jesper, > Here is the updated patch. > > From 92633f6819423093932e8d04aa3dc99a5913f6fd Mon Sep 17 00:00:00 2001 > From: Carlos Neira > 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