From: Nathan Chancellor <nathan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Lucas De Marchi" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"DRM XE List" <intel-xe@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Michal Wajdeczko" <michal.wajdeczko@intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Zongyao Bai" <zongyao.bai@intel.com>
Subject: Re: linux-next: manual merge of the drm-xe tree with the drm-fixes tree
Date: Mon, 22 Sep 2025 11:28:32 -0700 [thread overview]
Message-ID: <20250922182832.GA1542561@ax162> (raw)
In-Reply-To: <aM1QX4eEaSRQX6Dl@sirena.org.uk>
Hi Mark,
On Fri, Sep 19, 2025 at 01:45:19PM +0100, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the drm-xe tree got a conflict in:
>
> drivers/gpu/drm/xe/xe_guc_submit.c
>
> between commit:
>
> ff89a4d285c82 ("drm/xe/sysfs: Add cleanup action in xe_device_sysfs_init")
>
> from the drm-fixes tree and commit:
>
> fb3c27a69c473 ("drm/xe/sysfs: Simplify sysfs registration")
>
> from the drm-xe tree.
>
> I fixed it up (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.
>
> diff --cc drivers/gpu/drm/xe/xe_device_sysfs.c
> index b7f8fcfed8d86,c5151c86a98ae..0000000000000
> --- a/drivers/gpu/drm/xe/xe_device_sysfs.c
> +++ b/drivers/gpu/drm/xe/xe_device_sysfs.c
> @@@ -308,19 -290,15 +290,15 @@@ int xe_device_sysfs_init(struct xe_devi
> return ret;
> }
>
> - if (xe->info.platform == XE_BATTLEMAGE) {
> - ret = sysfs_create_files(&dev->kobj, auto_link_downgrade_attrs);
> + if (xe->info.platform == XE_BATTLEMAGE && !IS_SRIOV_VF(xe)) {
> + ret = devm_device_add_group(dev, &auto_link_downgrade_attr_group);
> if (ret)
> - return ret;
> + goto cleanup;
>
> - ret = late_bind_create_files(dev);
> + ret = devm_device_add_group(dev, &late_bind_attr_group);
> if (ret)
> - return ret;
> + goto cleanup;
> }
>
> - return devm_add_action_or_reset(dev, xe_device_sysfs_fini, xe);
> -
> - cleanup:
> - xe_device_sysfs_fini(xe);
> - return ret;
> + return 0;
> }
This resolution breaks the build.
drivers/gpu/drm/xe/xe_device_sysfs.c: In function 'xe_device_sysfs_init':
drivers/gpu/drm/xe/xe_device_sysfs.c:300:25: error: label 'cleanup' used but not defined
300 | goto cleanup;
| ^~~~
I think those should just be 'return ret', as it appears that
fb3c27a69c473 already includes ff89a4d285c82, so I think you can just
take the right side of the conflict wholesale.
Cheers,
Nathan
next prev parent reply other threads:[~2025-09-22 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 12:45 linux-next: manual merge of the drm-xe tree with the drm-fixes tree Mark Brown
2025-09-22 18:28 ` Nathan Chancellor [this message]
2025-09-22 19:25 ` Lucas De Marchi
-- strict thread matches above, loose matches on Subject: below --
2026-01-30 16:05 Mark Brown
2026-01-23 15:34 Mark Brown
2025-09-19 12:49 Mark Brown
2024-12-06 12:55 Mark Brown
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=20250922182832.GA1542561@ax162 \
--to=nathan@kernel.org \
--cc=broonie@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=zongyao.bai@intel.com \
/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