Linux driver-core infrastructure
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stuart Summers <stuart.summers@intel.com>
Cc: driver-core@lists.linux.dev,
	bartosz.golaszewski@oss.qualcomm.com,
	balasubramani.vivekanandan@intel.com,
	intel-xe@lists.freedesktop.org, heikki.krogerus@linux.intel.com,
	dakr@kernel.org
Subject: Re: [PATCH] driver core: platform: tests: add a shared software node test case
Date: Thu, 5 Nov 2026 00:04:17 +0200	[thread overview]
Message-ID: <auur4ZlHSB97uiKH@ashevche-desk.local> (raw)
In-Reply-To: <20261104202419.30180-2-stuart.summers@intel.com>

On Wed, Nov 04, 2026 at 08:24:16PM +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
> RIP: platform_device_release+0x6f/0x80

> Signed-off-by: Stuart Summers <stuart.summers@intel.com>
> Assisted-by: LLM
> 
> [1]: https://patchwork.freedesktop.org/series/175858/

This is wrongly formatter tag block, also URL can be made a Link tag.
On top, Assisted-by is obsolete.

At the result it's expected to be

  Link: https://patchwork.freedesktop.org/series/175858/ [1]
  Signed-off-by: Stuart Summers <stuart.summers@intel.com>

And last, but not least — thanks for the test cases! It's always appreciated.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-11-04 22:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 20:24 [PATCH] driver core: platform: tests: add a shared software node test case Stuart Summers
2026-11-04 22:04 ` Andy Shevchenko [this message]
2026-11-04 22:51   ` Summers, Stuart

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=auur4ZlHSB97uiKH@ashevche-desk.local \
    --to=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 \
    --cc=stuart.summers@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