All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Summers, Stuart" <stuart.summers@intel.com>
Cc: "andriy.shevchenko@linux.intel.com"
	<andriy.shevchenko@linux.intel.com>,
	"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>,
	"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: Fri, 20 Nov 2026 00:39:31 +0100	[thread overview]
Message-ID: <DMZL176U197K.X7ODAO4CRAOY@kernel.org> (raw)
In-Reply-To: <c45020ffef39314cee4093ba54e6ce7e0b1b187a.camel@intel.com>

On Thu Nov 19, 2026 at 11:37 PM CET, Stuart Summers wrote:
> 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?

This can be fixed up on apply.

Did you check the Sashiko feedback?

  reply	other threads:[~2026-11-19 23:39 UTC|newest]

Thread overview: 11+ 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-18 22:49   ` sashiko-bot
2026-11-19 13:37     ` Bartosz Golaszewski
2026-11-19 22:35       ` Summers, Stuart
2026-11-19 20:50   ` Andy Shevchenko
2026-11-19 22:37     ` Summers, Stuart
2026-11-19 23:39       ` Danilo Krummrich [this message]
2026-11-19  4:37 ` ✓ CI.KUnit: success for Add a shared software node test case to driver core Patchwork
2026-11-19  5:15 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-20  5:51 ` ✓ Xe.CI.FULL: " Patchwork

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=DMZL176U197K.X7ODAO4CRAOY@kernel.org \
    --to=dakr@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=balasubramani.vivekanandan@intel.com \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.