rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Lyude Paul <lyude@redhat.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"open list:RUST:Keyword:b(?i:rust)b"
	<rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH] iosys_map: Make dst a const in iosys_map_memcpy_to()
Date: Fri, 17 Oct 2025 09:45:04 +0200	[thread overview]
Message-ID: <8cb49212-99e7-4eae-ab8c-a95f3c81854d@suse.de> (raw)
In-Reply-To: <20251016202455.2750217-1-lyude@redhat.com>

Hi

Am 16.10.25 um 22:24 schrieb Lyude Paul:
> A drive-by fix I discovered when writing up bindings for iosys_mem for
> rust: while iosys_map_memcpy_to() does modify the memory pointed to by the
> iosys_map, it doesn't modify the actual iosys_map struct at all.
>
> As such, let's add a const qualifier to this function.

As far as I'm concerned, the non-const is intentional. Because it's the 
destination, so expect it to be written. Thus passing arguments that are 
already const is most likely an error. And because I'd like to keep the 
option of doing something more complicated within iosys_map (e.g., some 
temp memory for handling I/O) and const might get in the way.

Best regads
Thomas

>
> Signed-off-by: Lyude Paul <lyude@redhat.com>
> ---
>   include/linux/iosys-map.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/iosys-map.h b/include/linux/iosys-map.h
> index 3e85afe794c0a..0ececbba04b3a 100644
> --- a/include/linux/iosys-map.h
> +++ b/include/linux/iosys-map.h
> @@ -278,7 +278,7 @@ static inline void iosys_map_clear(struct iosys_map *map)
>    * system memory. Depending on the buffer's location, the helper picks the
>    * correct method of accessing the memory.
>    */
> -static inline void iosys_map_memcpy_to(struct iosys_map *dst, size_t dst_offset,
> +static inline void iosys_map_memcpy_to(const struct iosys_map *dst, size_t dst_offset,
>   				       const void *src, size_t len)
>   {
>   	if (dst->is_iomem)
>
> base-commit: 3a8660878839faadb4f1a6dd72c3179c1df56787

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)



      reply	other threads:[~2025-10-17  7:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 20:24 [PATCH] iosys_map: Make dst a const in iosys_map_memcpy_to() Lyude Paul
2025-10-17  7:45 ` Thomas Zimmermann [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=8cb49212-99e7-4eae-ab8c-a95f3c81854d@suse.de \
    --to=tzimmermann@suse.de \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    /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;
as well as URLs for NNTP newsgroup(s).