All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Gleb Natapov <gleb@kernel.org>, KVM <kvm@vger.kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the kvm tree
Date: Fri, 11 Aug 2017 14:36:24 +0200	[thread overview]
Message-ID: <20170811123623.GA28649@flask> (raw)
In-Reply-To: <31a4ba52-fc76-7844-841c-5f15142d473d@redhat.com>

2017-08-11 08:29+0200, David Hildenbrand:
> On 11.08.2017 01:28, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Commit
> > 
> >   53a70daf3cfd ("KVM: nVMX: get rid of nested_release_page*")
> > 
> > is missing a Signed-off-by from its committer.
> > 
> 
> Thanks,
> 
> Paolo's signed-off is missing.

Yes, it is a result of our workflow and there are many more patches like
that.  In this case, I originally committed the patch on 08-03 and Paolo
rebased the branch on 08-07.

We rebase when testing discovers bugs and for the first few release
candidates (when there are not enough changes to put into next).

Should all rebases be done with the --signoff option?

Thanks.

  reply	other threads:[~2017-08-11 12:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 23:28 linux-next: Signed-off-by missing for commit in the kvm tree Stephen Rothwell
2017-08-11  6:29 ` David Hildenbrand
2017-08-11 12:36   ` Radim Krčmář [this message]
2017-08-11 14:01     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2018-08-06 21:39 Stephen Rothwell
2018-08-06 21:55 ` Paolo Bonzini
2018-12-21 13:57 Stephen Rothwell
2020-01-23 20:43 Stephen Rothwell
2020-04-19 22:26 Stephen Rothwell
2020-04-20 22:32 Stephen Rothwell
2020-06-11  1:04 Stephen Rothwell
2020-08-04 22:29 Stephen Rothwell
2021-02-04 20:18 Stephen Rothwell
2021-02-05 14:36 ` Joao Martins
2021-09-30 22:42 Stephen Rothwell
2021-12-16 18:52 Stephen Rothwell
2022-01-08  7:24 Stephen Rothwell
2022-03-21 13:07 Stephen Rothwell
2022-05-22  0:51 Stephen Rothwell
2022-05-23 22:33 Stephen Rothwell

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=20170811123623.GA28649@flask \
    --to=rkrcmar@redhat.com \
    --cc=david@redhat.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.