All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Oliver Upton <oliver.upton@linux.dev>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH 00/10] KVM: arm64: fix many kernel-doc warnings
Date: Thu, 01 Feb 2024 13:45:04 +0000	[thread overview]
Message-ID: <86le8470yn.wl-maz@kernel.org> (raw)
In-Reply-To: <618cb278-0b9f-4cc2-bfc6-bfcbefc79b69@infradead.org>

On Thu, 01 Feb 2024 06:19:14 +0000,
Randy Dunlap <rdunlap@infradead.org> wrote:
> 
> Hi,
>
> Any comments on this series?

This is currently earmarked for 6.9.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Oliver Upton <oliver.upton@linux.dev>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH 00/10] KVM: arm64: fix many kernel-doc warnings
Date: Thu, 01 Feb 2024 13:45:04 +0000	[thread overview]
Message-ID: <86le8470yn.wl-maz@kernel.org> (raw)
In-Reply-To: <618cb278-0b9f-4cc2-bfc6-bfcbefc79b69@infradead.org>

On Thu, 01 Feb 2024 06:19:14 +0000,
Randy Dunlap <rdunlap@infradead.org> wrote:
> 
> Hi,
>
> Any comments on this series?

This is currently earmarked for 6.9.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-02-01 13:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 23:07 [PATCH 00/10] KVM: arm64: fix many kernel-doc warnings Randy Dunlap
2024-01-17 23:07 ` Randy Dunlap
2024-01-17 23:07 ` [PATCH 01/10] KVM: arm64: debug: fix " Randy Dunlap
2024-01-17 23:07   ` Randy Dunlap
2024-01-17 23:07 ` [PATCH 02/10] KVM: arm64: guest: " Randy Dunlap
2024-01-17 23:07   ` Randy Dunlap
2024-01-17 23:07 ` [PATCH 03/10] KVM: arm64: hyp/aarch32: " Randy Dunlap
2024-01-17 23:07   ` Randy Dunlap
2024-01-17 23:07 ` [PATCH 04/10] KVM: arm64: vhe: fix a kernel-doc warning Randy Dunlap
2024-01-17 23:07   ` Randy Dunlap
2024-01-17 23:07 ` [PATCH 05/10] KVM: arm64: mmu: " Randy Dunlap
2024-01-17 23:07   ` Randy Dunlap
2024-01-17 23:07 ` [PATCH 06/10] KVM: arm64: PMU: fix kernel-doc warnings Randy Dunlap
2024-01-17 23:07   ` Randy Dunlap
2024-01-17 23:07 ` [PATCH 07/10] KVM: arm64: sys_regs: " Randy Dunlap
2024-01-17 23:07   ` Randy Dunlap
2024-01-17 23:07 ` [PATCH 08/10] KVM: arm64: vgic-init: fix a kernel-doc warning Randy Dunlap
2024-01-17 23:07   ` Randy Dunlap
2024-01-17 23:07 ` [PATCH 09/10] KVM: arm64: vgic-its: fix kernel-doc warnings Randy Dunlap
2024-01-17 23:07   ` Randy Dunlap
2024-01-17 23:07 ` [PATCH 10/10] KVM: arm64: vgic: fix a kernel-doc warning Randy Dunlap
2024-01-17 23:07   ` Randy Dunlap
2024-02-01  6:19 ` [PATCH 00/10] KVM: arm64: fix many kernel-doc warnings Randy Dunlap
2024-02-01  6:19   ` Randy Dunlap
2024-02-01 13:45   ` Marc Zyngier [this message]
2024-02-01 13:45     ` Marc Zyngier
2024-02-01 17:47     ` Oliver Upton
2024-02-01 17:47       ` Oliver Upton
2024-02-01 10:23 ` Suzuki K Poulose
2024-02-01 10:23   ` Suzuki K Poulose
2024-02-01 13:49 ` Zenghui Yu
2024-02-01 13:49   ` Zenghui Yu
2024-02-01 20:30 ` Oliver Upton
2024-02-01 20:30   ` Oliver Upton

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=86le8470yn.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=rdunlap@infradead.org \
    --cc=suzuki.poulose@arm.com \
    --cc=will@kernel.org \
    --cc=yuzenghui@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 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.