linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joao Martins <joao.m.martins@oracle.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: David Woodhouse <dwmw@amazon.co.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	KVM <kvm@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the kvm tree
Date: Fri, 5 Feb 2021 14:36:44 +0000	[thread overview]
Message-ID: <37cae84d-3ef2-f5fc-0dae-55b3d346ef3b@oracle.com> (raw)
In-Reply-To: <20210205071821.7cbcb8b8@canb.auug.org.au>

On 2/4/21 8:18 PM, Stephen Rothwell wrote:
> Hi all,
> 
> Commit
> 
>   79033bebf6fa ("KVM: x86/xen: Fix coexistence of Xen and Hyper-V hypercalls")
> 
> is missing a Signed-off-by from its author.
> 
Except that David is the author of this particular patch, not me.

	Joao

  reply	other threads:[~2021-02-05 17:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 20:18 linux-next: Signed-off-by missing for commit in the kvm tree Stephen Rothwell
2021-02-05 14:36 ` Joao Martins [this message]
2021-02-05 14:38   ` [EXTERNAL] " David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2022-05-23 22:33 Stephen Rothwell
2022-05-22  0:51 Stephen Rothwell
2022-03-21 13:07 Stephen Rothwell
2022-01-08  7:24 Stephen Rothwell
2021-12-16 18:52 Stephen Rothwell
2021-09-30 22:42 Stephen Rothwell
2020-08-04 22:29 Stephen Rothwell
2020-06-11  1:04 Stephen Rothwell
2020-04-20 22:32 Stephen Rothwell
2020-04-19 22:26 Stephen Rothwell
2020-01-23 20:43 Stephen Rothwell
2018-12-21 13:57 Stephen Rothwell
2018-08-06 21:39 Stephen Rothwell
2018-08-06 21:55 ` Paolo Bonzini
2017-08-10 23:28 Stephen Rothwell
2017-08-11  6:29 ` David Hildenbrand
2017-08-11 12:36   ` Radim Krčmář
2017-08-11 14:01     ` 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=37cae84d-3ef2-f5fc-0dae-55b3d346ef3b@oracle.com \
    --to=joao.m.martins@oracle.com \
    --cc=dwmw@amazon.co.uk \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 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).