From: Andreas Hindborg <a.hindborg@kernel.org>
To: leitao@debian.org, Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/2] configfs: Constify some fileds in struct config_item_type
Date: Thu, 27 Nov 2025 12:12:11 +0100 [thread overview]
Message-ID: <176424193166.680817.14663362702382532392.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1761390472.git.christophe.jaillet@wanadoo.fr>
On Sat, 25 Oct 2025 13:15:36 +0200, Christophe JAILLET wrote:
> These 2 patches constify ct_item_ops and ct_group_ops in struct
> config_item_type.
>
> When/if they are applied, I'll send some patchess in each subsystem to
> constify the corresponding structures.
>
> This 2 steps approach is IMHO easier way to make these changes.
> This avoids long series and cover-letter/first patches sent to many
> maintainers and lists.
>
> [...]
Applied, thanks!
[1/2] configfs: Constify ct_group_ops in struct config_item_type
commit: f2f36500a63b73a8be90127322ad740253cf89c0
[2/2] configfs: Constify ct_item_ops in struct config_item_type
commit: f7f78098690d60a03b47942ac7d73ea17b42239e
Best regards,
--
Andreas Hindborg <a.hindborg@kernel.org>
prev parent reply other threads:[~2025-11-27 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <UMPsw5UqjtBaIrv5LPKiow0sOdVevbuvSx39jhXV_gtjHReEeeqGpgijGJj5OoJjMJA3mDIeSyzR9lffgIOr6g==@protonmail.internalid>
2025-10-25 11:15 ` Christophe JAILLET
2025-10-25 11:15 ` [PATCH 1/2] configfs: Constify ct_group_ops " Christophe JAILLET
2025-11-04 10:12 ` Breno Leitao
2025-10-25 11:15 ` [PATCH 2/2] configfs: Constify ct_item_ops " Christophe JAILLET
2025-11-04 10:10 ` Breno Leitao
2025-10-29 7:18 ` [PATCH 0/2] configfs: Constify some fileds " Andreas Hindborg
2025-11-01 13:13 ` Christophe JAILLET
2025-11-01 15:02 ` Andreas Hindborg
2025-11-27 11:12 ` Andreas Hindborg [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=176424193166.680817.14663362702382532392.b4-ty@kernel.org \
--to=a.hindborg@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®