All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ning, Hongyu" <hongyu.ning@linux.intel.com>
To: sfr@canb.auug.org.au
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	kirill.shutemov@linux.intel.com
Subject: linux-next tag next-240709: potential bug from commit "28ab42489515 Merge branch 'linux-next' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git"
Date: Fri, 12 Jul 2024 11:53:55 +0800	[thread overview]
Message-ID: <8804c63f-bca7-40c6-8be7-7b7bcfb66dec@linux.intel.com> (raw)


Hi all,

on a local linux-next (KVM/QEMU based guest kernel target) regular 
regression check environment, found a potential regression issue 
introduced by "28ab42489515 Merge branch 'linux-next' of 
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git",

detailed tracked in https://bugzilla.kernel.org/show_bug.cgi?id=219034

would you help to check it?

please let me know if any further track/debug needed.

-=Hongyu Ning

                 reply	other threads:[~2024-07-12  3:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8804c63f-bca7-40c6-8be7-7b7bcfb66dec@linux.intel.com \
    --to=hongyu.ning@linux.intel.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=xuanzhuo@linux.alibaba.com \
    /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.