From: Paolo Bonzini <pbonzini@redhat.com>
To: Yang Zhong <yang.zhong@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
tony.luck@intel.com, seanjc@google.com, vkuznets@redhat.com,
wanpengli@tencent.com, jmattson@google.com, joro@8bytes.org,
kyung.min.park@intel.com, x86@kernel.org
Subject: Re: [PATCH 1/2] Enumerate AVX Vector Neural Network instructions
Date: Wed, 13 Jan 2021 13:54:52 +0100 [thread overview]
Message-ID: <be47fd98-9d76-a35f-3ee2-7de2144dbdd6@redhat.com> (raw)
In-Reply-To: <20210112021321.GA9922@yangzhon-Virtual>
>>> Boris, is it possible to have a topic branch for this patch?
>>
>> Just take it through your tree pls.
>>
>> Acked-by: Borislav Petkov <bp@suse.de>
>>
>
> Paolo, Boris has acked this kernel patch, and if i need send new patchset to add this
> acked-by info ? or kvm tree will directly pull this patchset? thanks.
I'll take care of it shortly.
Paolo
next prev parent reply other threads:[~2021-01-13 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 0:49 [PATCH 0/2] Enumerate and expose AVX_VNNI feature Yang Zhong
2021-01-05 0:49 ` [PATCH 1/2] Enumerate AVX Vector Neural Network instructions Yang Zhong
2021-01-05 11:47 ` Paolo Bonzini
2021-01-05 12:14 ` Borislav Petkov
2021-01-12 2:13 ` Yang Zhong
2021-01-13 12:54 ` Paolo Bonzini [this message]
2021-01-05 0:49 ` [PATCH 2/2] KVM: Expose AVX_VNNI instruction to guset Yang Zhong
2021-01-21 15:02 ` [PATCH 0/2] Enumerate and expose AVX_VNNI feature Paolo Bonzini
2021-01-22 6:43 ` Yang Zhong
-- strict thread matches above, loose matches on Subject: below --
2020-12-16 2:01 Yang Zhong
2020-12-16 2:01 ` [PATCH 1/2] Enumerate AVX Vector Neural Network instructions Yang Zhong
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=be47fd98-9d76-a35f-3ee2-7de2144dbdd6@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=kyung.min.park@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=yang.zhong@intel.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.