From: Wei Liu <wei.liu@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Saurabh Sengar <ssengar@linux.microsoft.com>,
wei.liu@kernel.org, tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
kys@microsoft.com, haiyangz@microsoft.com, decui@microsoft.com,
tiala@microsoft.com, mikelley@microsoft.com,
linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix for applied series [PATCH v5 0/5] Hyper-V VTL support
Date: Tue, 18 Apr 2023 17:27:55 +0000 [thread overview]
Message-ID: <ZD7TGzJg1tSYt3jL@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <ZD7CllwJv7aAB4vO@liuwe-devbox-debian-v2>
On Tue, Apr 18, 2023 at 04:17:26PM +0000, Wei Liu wrote:
> On Tue, Apr 18, 2023 at 11:33:21AM +0200, Borislav Petkov wrote:
> > On Mon, Apr 17, 2023 at 10:12:39PM -0700, Saurabh Sengar wrote:
> > > [PATCH v5 0/5] Hyper-V VTL support is already applied, however
> > > there are couple of kernel test bot warning reported. This patch
> > > series on top of [PATCH v5 0/5] Hyper-V VTL support fixes these.
> > > I expect them to be squash commit on respective patches.
> >
> > That was supposed to happen when applying those using -rc7 as a base.
> >
> > Wei, what's up?
>
> I did use -rc7 as the base. This is what is in hyperv-next right now.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-next&id=25dcc7316ef7def25cdab3658ac665bf0ce0ddc5
>
> I think Saurabh was responding to a report that was generated on his v5
> series. I don't think the first patch is needed.
Never mind, I think I messed up when applying Saurabh's patch. I will
fix the tree today.
Thanks,
Wei.
prev parent reply other threads:[~2023-04-18 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 5:12 [PATCH 0/2] Fix for applied series [PATCH v5 0/5] Hyper-V VTL support Saurabh Sengar
2023-04-18 5:12 ` [PATCH 1/2] x86/init: Remove static for get/set_rtc_noop() Saurabh Sengar
2023-04-18 5:12 ` [PATCH 2/2] x86/hyperv: Allow hv_get_nmi_reason compilation irrespective of HYPERV config Saurabh Sengar
2023-04-18 9:33 ` [PATCH 0/2] Fix for applied series [PATCH v5 0/5] Hyper-V VTL support Borislav Petkov
2023-04-18 16:17 ` Wei Liu
2023-04-18 17:27 ` Wei Liu [this message]
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=ZD7TGzJg1tSYt3jL@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=ssengar@linux.microsoft.com \
--cc=tglx@linutronix.de \
--cc=tiala@microsoft.com \
--cc=x86@kernel.org \
/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