linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	Networking <netdev@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the bpf-next tree
Date: Wed, 12 Dec 2018 15:39:10 -0800	[thread overview]
Message-ID: <20181212233909.hhf5q4vpi3mmi37u@ast-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20181213094820.62d26354@canb.auug.org.au>

On Thu, Dec 13, 2018 at 09:48:20AM +1100, Stephen Rothwell wrote:
> Hi Alexei,
> 
> On Wed, 12 Dec 2018 12:53:11 -0800 Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> >
> > On Thu, Dec 13, 2018 at 07:32:45AM +1100, Stephen Rothwell wrote:
> > > Hi all,
> > > 
> > > Commits
> > > 
> > >   3bdc28aa2340 ("selftests/bpf: add btf annotations for cgroup_local_storage maps")
> > >   1dfd1959fed4 ("bpf: add bpffs pretty print for cgroup local storage maps")
> > >   3adc62d9a5be ("bpf: pass struct btf pointer to the map_check_btf() callback")
> > >   9cf3a785dc4c ("selftests/bpf: use __bpf_constant_htons in test_prog.c")
> > > 
> > > are missing a Signed-off-by from their committers.  
> > 
> > the must be a script mistake?
> > 
> > I clearly see SOBs for all of them.
> 
> For example:
> 
> commit 3bdc28aa2340bf1e5af753287b373522bd1c02a9 (bpf-next/master)
> Author: Roman Gushchin <guroan@gmail.com>
> Date:   Mon Dec 10 15:43:02 2018 -0800
> 
>     selftests/bpf: add btf annotations for cgroup_local_storage maps
>     
>     Add btf annotations to cgroup local storage maps (per-cpu and shared)
>     in the network packet counting example.
>     
>     Signed-off-by: Roman Gushchin <guro@fb.com>
>     Cc: Alexei Starovoitov <ast@kernel.org>
>     Cc: Daniel Borkmann <daniel@iogearbox.net>
>     Acked-by: Martin KaFai Lau <kafai@fb.com>
>     Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> 
> But it was committed by you, not Daniel.

since there were only 4 commits I fixed them up manually.
But this approach doesn't scale.
We do rebase our trees when we need to fixup or drop patches and
at any given point a number of commits will be committed by me
and another set by Daniel. When we rebase we cannot keep adding
our SOBs to the other person SOBs.
Then comes the next rebase and we get to the point of
double and triple SOBs ?

I think you need to adjust the script to something like:
SOBs by Daniel | Alexei == commit by Daniel | Alexei
in bpf and bpf-next trees.

  reply	other threads:[~2018-12-12 23:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 20:32 linux-next: Signed-off-by missing for commits in the bpf-next tree Stephen Rothwell
2018-12-12 20:53 ` Alexei Starovoitov
2018-12-12 22:48   ` Stephen Rothwell
2018-12-12 23:39     ` Alexei Starovoitov [this message]
2018-12-12 23:45       ` Bart Van Assche
2018-12-13  0:20         ` Alexei Starovoitov
2018-12-13  0:45       ` David Miller
2018-12-13  4:33         ` Alexei Starovoitov
2018-12-13  5:37           ` Stephen Rothwell
2018-12-13  5:45             ` Alexei Starovoitov

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=20181212233909.hhf5q4vpi3mmi37u@ast-mbp.dhcp.thefacebook.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).