From: Wei Liu <wei.liu@kernel.org>
To: Naman Jain <namjain@linux.microsoft.com>
Cc: "K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
John Starks <jostarks@microsoft.com>,
jacob.pan@linux.microsoft.com,
Easwar Hariharan <eahariha@linux.microsoft.com>,
Michael Kelley <mhklinux@outlook.com>,
Saurabh Singh Sengar <ssengar@linux.microsoft.com>
Subject: Re: [PATCH v4 0/2] Drivers: hv: vmbus: Wait for boot-time offers and log missing offers
Date: Tue, 24 Dec 2024 05:19:35 +0000 [thread overview]
Message-ID: <Z2pEZycwPkLAFfVQ@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20241118070725.3221-1-namjain@linux.microsoft.com>
On Sun, Nov 17, 2024 at 11:07:23PM -0800, Naman Jain wrote:
[...]
> John Starks (1):
> Drivers: hv: vmbus: Log on missing offers if any
>
> Naman Jain (1):
> Drivers: hv: vmbus: Wait for boot-time offers during boot and resume
>
> drivers/hv/channel_mgmt.c | 61 +++++++++++++++++++++++++++++----------
> drivers/hv/connection.c | 4 +--
> drivers/hv/hyperv_vmbus.h | 14 ++-------
> drivers/hv/vmbus_drv.c | 31 ++++++++++----------
> 4 files changed, 67 insertions(+), 43 deletions(-)
Can you please rebase on top of the latest hyperv-next? There are some
conflicts now.
Thanks,
Wei.
prev parent reply other threads:[~2024-12-24 5:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 7:07 [PATCH v4 0/2] Drivers: hv: vmbus: Wait for boot-time offers and log missing offers Naman Jain
2024-11-18 7:07 ` [PATCH v4 1/2] Drivers: hv: vmbus: Wait for boot-time offers during boot and resume Naman Jain
2024-11-18 7:07 ` [PATCH v4 2/2] Drivers: hv: vmbus: Log on missing offers if any Naman Jain
2024-12-24 5:19 ` 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=Z2pEZycwPkLAFfVQ@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=decui@microsoft.com \
--cc=eahariha@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jacob.pan@linux.microsoft.com \
--cc=jostarks@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=namjain@linux.microsoft.com \
--cc=ssengar@linux.microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox