From: Lyude Paul <lyude@redhat.com>
To: Maxime Ripard <mripard@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org (open
list:RUST:Keyword:b(?i:rust)b)
Subject: [PATCH 0/2] drm: Make some resolution info unsigned
Date: Tue, 25 Mar 2025 17:27:03 -0400 [thread overview]
Message-ID: <20250325212823.669459-1-lyude@redhat.com> (raw)
During the review of some of my patches for KMS bindings in Rust, it was
pointed out we have some areas of DRM that are storing resolutions as
signed integers when it doesn't really make sense. Since there's no real
usecase for this and it's a bit more obvious when writing rust code then
it is in C, let's fix this.
Lyude Paul (2):
drm/edid: Use unsigned int in drm_add_modes_noedid()
drm/mode_config: Make drm_mode_config.(max|min)_(width|height) signed
drivers/gpu/drm/drm_edid.c | 2 +-
include/drm/drm_edid.h | 2 +-
include/drm/drm_mode_config.h | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
base-commit: 5da39dce1fa3c81dc6552a16a9f748ba2980d630
--
2.48.1
next reply other threads:[~2025-03-25 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 21:27 Lyude Paul [this message]
2025-03-25 21:27 ` [PATCH 1/2] drm/edid: Use unsigned int in drm_add_modes_noedid() Lyude Paul
2025-03-26 9:29 ` Thomas Zimmermann
2025-03-26 10:39 ` Jani Nikula
2025-03-26 11:06 ` Miguel Ojeda
2025-03-28 22:27 ` Lyude Paul
2025-03-29 12:04 ` Miguel Ojeda
2025-03-26 9:07 ` [PATCH 0/2] drm: Make some resolution info unsigned Maxime Ripard
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=20250325212823.669459-1-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--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).