From: "Summers, Stuart" <stuart.summers@intel.com>
To: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Vivekanandan,
Balasubramani" <balasubramani.vivekanandan@intel.com>,
"driver-core@lists.linux.dev" <driver-core@lists.linux.dev>,
"bartosz.golaszewski@oss.qualcomm.com"
<bartosz.golaszewski@oss.qualcomm.com>,
"dakr@kernel.org" <dakr@kernel.org>,
"heikki.krogerus@linux.intel.com"
<heikki.krogerus@linux.intel.com>
Subject: Re: [PATCH 1/1] driver core: platform: tests: add a shared software node test case
Date: Thu, 19 Nov 2026 22:37:14 +0000 [thread overview]
Message-ID: <c45020ffef39314cee4093ba54e6ce7e0b1b187a.camel@intel.com> (raw)
In-Reply-To: <av9hGMZz0SZyxCQR@ashevche-desk.local>
On Thu, 2026-11-19 at 22:50 +0200, Andy Shevchenko wrote:
> On Wed, Nov 18, 2026 at 10:30:23PM +0000, Stuart Summers wrote:
> > Cover the pattern used by drm/xe + i2c-designware, where a software
> > node
> > assigned as a platform device's primary firmware node is handed to
> > a
> > second device via device_set_node(), and make sure removing that
> > second
> > device leaves the owner's node intact.
> >
> > A potential fix for this issue in the drm/xe driver is being
> > discussed
> > in [1].
> >
> > The signature in this case looks like this:
>
> > Oops: general protection fault, probably for non-canonical address
> > 0x6b6b6b6b6b6b6b73
>
> This probably was a single line, make it so in the commit message
> despite its
> length.
Thanks for the review! Would you like me to fix that up and resend?
I'll likely need help merging so is this something that can be fixed up
as part of the merge?
Thanks,
Stuart
>
> > RIP: platform_device_release+0x6f/0x80
>
> ...
>
> Test cases are always warmly welcome!
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
next prev parent reply other threads:[~2026-11-19 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 22:30 [PATCH 0/1] Add a shared software node test case to driver core Stuart Summers
2026-11-18 22:30 ` [PATCH 1/1] driver core: platform: tests: add a shared software node test case Stuart Summers
2026-11-19 20:50 ` Andy Shevchenko
2026-11-19 22:37 ` Summers, Stuart [this message]
2026-11-19 23:39 ` Danilo Krummrich
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=c45020ffef39314cee4093ba54e6ce7e0b1b187a.camel@intel.com \
--to=stuart.summers@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=balasubramani.vivekanandan@intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=heikki.krogerus@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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