From: "Danilo Krummrich" <dakr@kernel.org>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: "Dave Airlie" <airlied@redhat.com>,
"Simona Vetter" <simona.vetter@ffwll.ch>,
"Beata Michalska" <beata.michalska@arm.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"DRI" <dri-devel@lists.freedesktop.org>,
"Intel Graphics" <intel-gfx@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the drm tree with the drm-misc-fixes tree
Date: Wed, 20 Aug 2025 12:30:14 +0200 [thread overview]
Message-ID: <DC76OGHHB0NH.2150TC0DHRN8A@kernel.org> (raw)
In-Reply-To: <20250820112144.43714c90@canb.auug.org.au>
On Wed Aug 20, 2025 at 3:21 AM CEST, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the drm tree got a conflict in:
>
> drivers/gpu/drm/nova/file.rs
>
> between commit:
>
> db2e7bcee11c ("drm: nova-drm: fix 32-bit arm build")
>
> from the drm-misc-fixes tree and commit:
>
> 94febfb5bcfb ("rust: drm: Drop the use of Opaque for ioctl arguments")
>
> from the drm tree.
>
> I fixed it up (I think - see below) and can carry the fix as
> necessary. This is now fixed as far as linux-next is concerned, but any
> non trivial conflicts should be mentioned to your upstream maintainer
> when your tree is submitted for merging. You may also want to consider
> cooperating with the maintainer of the conflicting tree to minimise any
> particularly complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc drivers/gpu/drm/nova/file.rs
> index 4fe62cf98a23,7e7d4e2de2fb..000000000000
> --- a/drivers/gpu/drm/nova/file.rs
> +++ b/drivers/gpu/drm/nova/file.rs
> @@@ -39,8 -36,7 +36,8 @@@ impl File
> _ => return Err(EINVAL),
> };
>
> - getparam.value = value;
> + #[allow(clippy::useless_conversion)]
> - getparam.set_value(value.into());
> ++ getparam.value = value.into();
>
> Ok(0)
> }
I think this resolution doesn't compile, since attributes on expressions are
behind an unstable feature flag.
I assume your config does not have CONFIG_DRM_NOVA={y,m}.
The resolution in [1] is the one I came up with in the drm-tip tree.
I should probably have given you a head-up on this conflict, sorry for that.
[1]
diff --cc drivers/gpu/drm/nova/file.rs
index 4fe62cf98a23,7e7d4e2de2fb..90b9d2d0ec4a
--- a/drivers/gpu/drm/nova/file.rs
+++ b/drivers/gpu/drm/nova/file.rs
@@@ -39,8 -36,7 +36,7 @@@ impl File
_ => return Err(EINVAL),
};
- #[allow(clippy::useless_conversion)]
- getparam.set_value(value.into());
- getparam.value = value;
++ getparam.value = Into::<u64>::into(value);
Ok(0)
}
next prev parent reply other threads:[~2025-08-20 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 1:21 linux-next: manual merge of the drm tree with the drm-misc-fixes tree Stephen Rothwell
2025-08-20 10:30 ` Danilo Krummrich [this message]
2025-08-20 21:29 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-07-18 4:41 Stephen Rothwell
2025-07-18 6:27 ` Thomas Zimmermann
2025-01-14 1:30 Stephen Rothwell
2019-08-26 3:06 Stephen Rothwell
2019-08-29 10:11 ` james qian wang (Arm Technology China)
2018-11-26 2:37 Stephen Rothwell
2018-03-08 0:47 Stephen Rothwell
2017-12-13 23:59 Stephen Rothwell
2017-01-17 0:59 Stephen Rothwell
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=DC76OGHHB0NH.2150TC0DHRN8A@kernel.org \
--to=dakr@kernel.org \
--cc=airlied@redhat.com \
--cc=beata.michalska@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=simona.vetter@ffwll.ch \
/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).