All of lore.kernel.org
 help / color / mirror / Atom feed
From: si-wei liu <si-wei.liu@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: 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 vhost tree
Date: Thu, 01 Oct 2020 16:03:42 -0700	[thread overview]
Message-ID: <5F76604E.6080304@oracle.com> (raw)
In-Reply-To: <20201002083200.685639e9@canb.auug.org.au>

Thanks Stephen, the SHA1 referenced is not correct. A v2 patch is posted.

Thanks,
-Siwei


On 10/1/2020 3:32 PM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
>    c9795f8fbb41 ("vhost-vdpa: fix page pinning leakage in error path")
>
> Fixes tag
>
>    Fixes: 20453a45fb06 ("vhost: introduce vDPA-based backend")
>
> has these problem(s):
>
>    - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 4c8cf31885f6 ("vhost: introduce vDPA-based backend")
>


  reply	other threads:[~2020-10-01 23:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 22:32 linux-next: Fixes tag needs some work in the vhost tree Stephen Rothwell
2020-10-01 23:03 ` si-wei liu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-07 22:22 Stephen Rothwell
2025-02-24 22:45 Stephen Rothwell
2025-02-25 12:12 ` Michael S. Tsirkin
2022-08-10 22:28 Stephen Rothwell
2021-10-24 21:23 Stephen Rothwell
2021-09-14 21:24 Stephen Rothwell
2021-09-13 23:23 Stephen Rothwell
2021-08-10 22:22 Stephen Rothwell
2021-04-22 22:43 Stephen Rothwell
2020-05-02  0:30 Stephen Rothwell
2020-05-05 15:16 ` Stefan Hajnoczi

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=5F76604E.6080304@oracle.com \
    --to=si-wei.liu@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mst@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.