Hi Linus,
The following changes since commit d206a76d7d2726f3b096037f2079ce0bd3ba329b:
Linux 6.8-rc6 (2024-02-25 15:46:06 -0800)
are available in the Git repository at:
ssh://[email protected]/pub/scm/linux/kernel/git/hyperv/linux.git tags/hyperv-next-signed-20240320
for you to fetch changes up to f2580a907e5c0e8fc9354fd095b011301c64f949:
x86/hyperv: Use Hyper-V entropy to seed guest random number generator (2024-03-18 22:01:52 +0000)
----------------------------------------------------------------
hyperv-next for v6.9
- Use Hyper-V entropy to seed guest random number generator (Michael Kelley)
- Convert to platform remove callback returning void for vmbus (Uwe Kleine-K?nig)
- Introduce hv_get_hypervisor_version function (Nuno Das Neves)
- Rename some HV_REGISTER_* defines for consistency (Nuno Das Neves)
- Change prefix of generic HV_REGISTER_* MSRs to HV_MSR_* (Nuno Das Neves)
- Cosmetic changes for hv_spinlock.c (Purna Pavan Chandra Aekkaladevi)
- Use per cpu initial stack for vtl context (Saurabh Sengar)
----------------------------------------------------------------
Michael Kelley (1):
x86/hyperv: Use Hyper-V entropy to seed guest random number generator
Nuno Das Neves (3):
hyperv-tlfs: Change prefix of generic HV_REGISTER_* MSRs to HV_MSR_*
mshyperv: Introduce hv_get_hypervisor_version function
hyperv-tlfs: Rename some HV_REGISTER_* defines for consistency
Purna Pavan Chandra Aekkaladevi (1):
x86/hyperv: Cosmetic changes for hv_spinlock.c
Saurabh Sengar (1):
x86/hyperv: Use per cpu initial stack for vtl context
Uwe Kleine-K?nig (1):
hv: vmbus: Convert to platform remove callback returning void
arch/arm64/hyperv/hv_core.c | 14 ++--
arch/arm64/hyperv/mshyperv.c | 22 +++---
arch/arm64/include/asm/hyperv-tlfs.h | 45 +++++------
arch/arm64/include/asm/mshyperv.h | 4 +-
arch/x86/hyperv/hv_init.c | 8 +-
arch/x86/hyperv/hv_spinlock.c | 3 +-
arch/x86/hyperv/hv_vtl.c | 19 ++++-
arch/x86/include/asm/hyperv-tlfs.h | 145 ++++++++++++++++++-----------------
arch/x86/include/asm/mshyperv.h | 30 ++++----
arch/x86/kernel/cpu/mshyperv.c | 93 +++++++++++-----------
drivers/clocksource/hyperv_timer.c | 26 +++----
drivers/hv/Kconfig | 1 +
drivers/hv/hv.c | 36 ++++-----
drivers/hv/hv_common.c | 99 +++++++++++++++++++++---
drivers/hv/vmbus_drv.c | 5 +-
include/asm-generic/hyperv-tlfs.h | 55 ++++++++++++-
include/asm-generic/mshyperv.h | 6 +-
17 files changed, 375 insertions(+), 236 deletions(-)
On Wed, 20 Mar 2024 at 21:09, Wei Liu <[email protected]> wrote:
>
> ssh://[email protected]/pub/scm/linux/kernel/git/hyperv/linux.git tags/hyperv-next-signed-20240320
Pulled, but...
Your pgp key expired two weeks ago. Please extend the expiration date
(and not something small!) and make sure to refresh the kernel.org
repo and/or other keyservers.
Linus
The pull request you sent on Thu, 21 Mar 2024 04:09:09 +0000:
> ssh://[email protected]/pub/scm/linux/kernel/git/hyperv/linux.git tags/hyperv-next-signed-20240320
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/cfce216e1439d67a52a4b4c709299f6555946c33
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
On Thu, Mar 21, 2024 at 10:06:53AM -0700, Linus Torvalds wrote:
> On Wed, 20 Mar 2024 at 21:09, Wei Liu <[email protected]> wrote:
> >
> > ssh://[email protected]/pub/scm/linux/kernel/git/hyperv/linux.git tags/hyperv-next-signed-20240320
>
> Pulled, but...
>
> Your pgp key expired two weeks ago. Please extend the expiration date
> (and not something small!) and make sure to refresh the kernel.org
> repo and/or other keyservers.
Hmm... I thought I refreshed it right before the expiration date. I
pushed it to Ubuntu's keyserver.
I will check if something's wrong.
Do you have a keyserver that you prefer?
Thanks,
Wei.
>
> Linus
On Fri, 22 Mar 2024 at 16:25, Wei Liu <[email protected]> wrote:
>
> Hmm... I thought I refreshed it right before the expiration date. I
> pushed it to Ubuntu's keyserver.
Ok, I can find it there.
> I will check if something's wrong.
>
> Do you have a keyserver that you prefer?
The problem with keyservers is that there's so many of them, and
everybody uses different keyservers, and the propagation of pgp keys
across keyservers hasn't really worked for over a decade by now.
Maybe keys eventually propagate, but I have my doubts.
My default keyserver appears to be hkps://keys.openpgp.org, but the
pgp key git tree on kernel.org is the one I then look at when some key
isn't there (or is there, but hasn't been updated).
Linus
On Fri, Mar 22, 2024 at 04:42:50PM -0700, Linus Torvalds wrote:
> On Fri, 22 Mar 2024 at 16:25, Wei Liu <[email protected]> wrote:
> >
> > Hmm... I thought I refreshed it right before the expiration date. I
> > pushed it to Ubuntu's keyserver.
>
> Ok, I can find it there.
>
> > I will check if something's wrong.
> >
> > Do you have a keyserver that you prefer?
>
> The problem with keyservers is that there's so many of them, and
> everybody uses different keyservers, and the propagation of pgp keys
> across keyservers hasn't really worked for over a decade by now.
I noticed that keys do eventually propagate, but I never had the means
to time how long it takes.
>
> Maybe keys eventually propagate, but I have my doubts.
>
> My default keyserver appears to be hkps://keys.openpgp.org, but the
> pgp key git tree on kernel.org is the one I then look at when some key
> isn't there (or is there, but hasn't been updated).
>
Okay, so my key in that git repository has not been updated. And the
last time it was updated was in Jan 2023 (!). I thought it was updated
more often by a cron job but apparently not.
I will drop an email to [email protected] to refresh the key.
Thanks,
Wei.
> Linus