From: David Hildenbrand <david@redhat.com>
To: Max Kellermann <max.kellermann@ionos.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
akpm@linux-foundation.org, Liam.Howlett@oracle.com,
vbabka@suse.cz, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: add `const` to lots of pointer parameters
Date: Thu, 28 Aug 2025 15:00:39 +0200 [thread overview]
Message-ID: <832e89d4-fc7c-47ad-b375-6af0ce796d42@redhat.com> (raw)
In-Reply-To: <CAKPOu+8DbXY6wT_8gcqLDpyZEg0=En6wOYtHX_VkUvZ_oOLHSg@mail.gmail.com>
On 28.08.25 14:40, Max Kellermann wrote:
>> On 28.08.25 14:24, Lorenzo Stoakes wrote:
>>> On Wed, Aug 27, 2025 at 09:22:33PM +0200, Max Kellermann wrote:
>>>> For improved const-correctness.
>>>
>>> 'const-correctness' in C is extremely weak.
>
> "const correctness" is a commonly used term for this concept, and I
> find your arguments against const-correctness "extremely weak". I
> don't think discussing the benefits of const-correctness is worth the
> time; the concept is trivial enough, and if you don't already agree,
> there is no way I can convince you. Let's agree to disagree.
>
> On Thu, Aug 28, 2025 at 2:29 PM David Hildenbrand <david@redhat.com> wrote:
>> I recall that Willy did some more targeted conversions of that kind in the past regarding folios.
>
> And I found many more commits adding "const" to pointer parameters.
> That shows this kind of patch is acceptable in the Linux kernel.
>
>> I would appreciate similarly doing it in logical chunks.
>
> So you suggest splitting the patch into many?
Yes, for example focusing on a specific class of functions like Willy did.
That makes my life as a maintainer and reviewer easier, and allows for
holding back some of these patches if we expect conflicts in that area soon.
/me stares helplessly at his overflowing inbox where #submitters is
significantly larger than #reviewers, and the majority of patches are
not in a form that would allow for any kinds of easy review.
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-08-28 13:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 19:22 Max Kellermann
2025-08-27 21:48 ` Andrew Morton
2025-08-28 1:48 ` Liam R. Howlett
2025-08-28 2:47 ` Andrew Morton
2025-08-28 12:09 ` Lorenzo Stoakes
2025-08-28 12:16 ` Max Kellermann
2025-08-28 12:35 ` Lorenzo Stoakes
2025-08-28 12:42 ` Max Kellermann
2025-08-28 12:49 ` Lorenzo Stoakes
2025-08-28 12:24 ` Lorenzo Stoakes
2025-08-28 12:28 ` David Hildenbrand
2025-08-28 12:40 ` Max Kellermann
2025-08-28 12:43 ` Lorenzo Stoakes
2025-08-28 12:51 ` Max Kellermann
2025-08-28 13:00 ` David Hildenbrand [this message]
2025-08-28 12:55 ` Lorenzo Stoakes
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=832e89d4-fc7c-47ad-b375-6af0ce796d42@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=max.kellermann@ionos.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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