From: liulongfang <liulongfang@huawei.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <alex.williamson@redhat.com>, <jgg@nvidia.com>,
<shameerali.kolothum.thodi@huawei.com>,
<jonathan.cameron@huawei.com>, <linux-crypto@vger.kernel.org>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@openeuler.org>
Subject: Re: [PATCH v7 2/3] migration: qm updates BAR configuration
Date: Tue, 19 Aug 2025 18:56:13 +0800 [thread overview]
Message-ID: <390b3bbb-34d1-04d1-6797-7d726b89cee3@huawei.com> (raw)
In-Reply-To: <aKRJpStZKhy8_5-V@gondor.apana.org.au>
On 2025/8/19 17:53, Herbert Xu wrote:
> On Tue, Aug 19, 2025 at 05:12:52PM +0800, liulongfang wrote:
>>
>> Hello, Herbert. There is a patch in this patchset that modifies the crypto subsystem.
>> Could this patch be merged into the crypto next branch?
>
> Does it depend on the other patches?
>
This patch does not depend on any other patches.
Thanks.
Longfang.
> Cheers,
>
next prev parent reply other threads:[~2025-08-19 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 6:51 [PATCH v7 0/3] update live migration configuration region Longfang Liu
2025-08-05 6:51 ` [PATCH v7 1/3] migration: update BAR space size Longfang Liu
2025-08-05 6:51 ` [PATCH v7 2/3] migration: qm updates BAR configuration Longfang Liu
2025-08-19 9:12 ` liulongfang
2025-08-19 9:53 ` Herbert Xu
2025-08-19 10:56 ` liulongfang [this message]
2025-08-05 6:51 ` [PATCH v7 3/3] migration: adapt to new migration configuration Longfang Liu
2025-08-19 21:35 ` Alex Williamson
2025-08-20 1:53 ` liulongfang
2025-08-19 9:14 ` [PATCH v7 0/3] update live migration configuration region liulongfang
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=390b3bbb-34d1-04d1-6797-7d726b89cee3@huawei.com \
--to=liulongfang@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jgg@nvidia.com \
--cc=jonathan.cameron@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=shameerali.kolothum.thodi@huawei.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
all inboxes | Powered by JetHome®