All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>
Cc: Claudio Imbrenda <imbrenda@linux.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the kvm tree
Date: Fri, 16 Apr 2021 14:38:04 +0200	[thread overview]
Message-ID: <00222197-fb22-ab0a-97e2-11c9f85a67f1@de.ibm.com> (raw)
In-Reply-To: <20210416222731.3e82b3a0@canb.auug.org.au>

On 16.04.21 14:27, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>    c3171e94cc1c ("KVM: s390: VSIE: fix MVPG handling for prefixing and MSO")
> 
> Fixes tag
> 
>    Fixes: bdf7509bbefa ("s390/kvm: VSIE: correctly handle MVPG when in VSIE")
> 
> has these problem(s):
> 
>    - Subject does not match target commit subject
>      Just use
> 	git log -1 --format='Fixes: %h ("%s")'

Hmm, this has been sitting in kvms390/next for some time now. Is this a new check?

  reply	other threads:[~2021-04-16 12:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 12:27 linux-next: Fixes tag needs some work in the kvm tree Stephen Rothwell
2021-04-16 12:38 ` Christian Borntraeger [this message]
2021-04-16 14:02   ` Paolo Bonzini
2021-04-16 14:58     ` Stephen Rothwell
2021-04-16 15:02       ` Christian Borntraeger
  -- strict thread matches above, loose matches on Subject: below --
2024-01-09 21:31 Stephen Rothwell
2022-07-20 22:05 Stephen Rothwell
2022-05-22  0:49 Stephen Rothwell
2022-01-19 11:49 Stephen Rothwell
2021-09-06 21:48 Stephen Rothwell
2021-08-19 22:20 Stephen Rothwell
2021-06-21 22:18 Stephen Rothwell
2021-06-21 23:37 ` Paolo Bonzini
2021-02-04 20:16 Stephen Rothwell
2020-03-16 20:36 Stephen Rothwell
2020-01-24  3:13 Stephen Rothwell
2019-12-04 12:50 Stephen Rothwell
2019-02-16  7:34 Stephen Rothwell
2019-02-20  7:02 ` Yu Zhang

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=00222197-fb22-ab0a-97e2-11c9f85a67f1@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --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 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.