The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Ian Rogers" <irogers@google.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Kees Cook" <kees@kernel.org>, "Miguel Ojeda" <ojeda@kernel.org>,
	"Nick Desaulniers" <ndesaulniers@google.com>,
	<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/9] Add __must_init and require explicit kobj_type::release
Date: Wed, 18 Nov 2026 22:00:34 +0100	[thread overview]
Message-ID: <DMYN0YFVA1Q8.6EPKUPFPHVL9@kernel.org> (raw)
In-Reply-To: <CAP-5=fXEk-ommviDYeD6hMvsESJMHfajina4kjMw6NMuRfQmTg@mail.gmail.com>

On Wed Nov 18, 2026 at 6:12 PM CET, Ian Rogers wrote:
> Hi Danilo,
>
> Just a quick heads-up that all three remaining subsystem ACKs have now
> arrived on the v3 thread:
>  - 2/9 (powerpc/secvar): Acked-by Madhavan Srinivasan, Reviewed-by
> Srish Srinivasan
>  - 3/9 (sh: sq): Acked-by John Paul Adrian Glaubitz
>  - 6/9 (xen/sys-hypervisor): Reviewed-by Juergen Gross
>
> v3 still applies cleanly to driver-core-next (and b4 picks up all the
> tags). Sashiko did flag more accurate Fixes: SHAs on 5/9
> (8a4cf500f1dd) and 7/9 (2e3cbf425804) — happy to send a quick v4 with
> those and the new tags folded in if you prefer, otherwise v3 is ready
> as-is.

No need to respin for tags, but I think it would be good to respin for the last
patch, I will leave a comment there.

Thanks,
Danilo

      reply	other threads:[~2026-11-18 21:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08 22:39 [PATCH v3 0/9] Add __must_init and require explicit kobj_type::release Ian Rogers
2026-11-08 22:39 ` [PATCH v3 1/9] Compiler Attributes: Add __must_init macro Ian Rogers
2026-11-08 22:39 ` [PATCH v3 2/9] powerpc/secvar: Add missing kobject release callback to secvar_ktype Ian Rogers
2026-11-17 20:25   ` Ian Rogers
2026-11-18 11:27     ` Madhavan Srinivasan
2026-11-18  8:17   ` Srish Srinivasan
2026-11-08 22:39 ` [PATCH v3 3/9] sh: sq: Add missing kobject release callback to ktype_percpu_entry Ian Rogers
2026-11-17 20:28   ` Ian Rogers
2026-11-18  7:18     ` John Paul Adrian Glaubitz
2026-11-18  7:20   ` John Paul Adrian Glaubitz
2026-11-08 22:39 ` [PATCH v3 4/9] cpufreq: governor: Initialize kobj_type release callback statically Ian Rogers
2026-11-08 22:39 ` [PATCH v3 5/9] dlm: Free dlm_ls in kobject release callback Ian Rogers
2026-11-08 22:39 ` [PATCH v3 6/9] xen/sys-hypervisor: Add release callback to hyp_sysfs_kobj_type Ian Rogers
2026-11-09  6:56   ` Juergen Gross
2026-11-09 22:29     ` Ian Rogers
2026-11-08 22:39 ` [PATCH v3 7/9] ubifs: sysfs: Use kset_create_and_add() for ubifs_kset Ian Rogers
2026-11-08 22:39 ` [PATCH v3 8/9] drm/amdkfd: Free queue in procfs_queue_type kobject release callback Ian Rogers
2026-11-08 22:39 ` [PATCH v3 9/9] kobject: Require explicit initialization of struct kobj_type::release Ian Rogers
2026-11-18 21:11   ` Danilo Krummrich
2026-11-18 17:12 ` [PATCH v3 0/9] Add __must_init and require explicit kobj_type::release Ian Rogers
2026-11-18 21:00   ` Danilo Krummrich [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=DMYN0YFVA1Q8.6EPKUPFPHVL9@kernel.org \
    --to=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=irogers@google.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=ojeda@kernel.org \
    /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