X86 platform drivers
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: jesse.huang@portwell.com.tw, Hans de Goede <hansg@kernel.org>,
	 Ivan Hu <ivan.hu@canonical.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: portwell-ec: Move watchdog device under correct platform hierarchy
Date: Tue, 17 Jun 2025 15:39:27 +0300	[thread overview]
Message-ID: <175016396784.2117.17760069143731319818.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250616074819.63547-1-ivan.hu@canonical.com>

On Mon, 16 Jun 2025 15:48:19 +0800, Ivan Hu wrote:

> Without explicitly setting a parent for the watchdog device, the device is
> registered with a NULL parent. This causes device_add() (called internally
> by devm_watchdog_register_device()) to register the device under
> /sys/devices/virtual, since no parent is provided. The result is:
> 
> DEVPATH=/devices/virtual/watchdog/watchdog0
> 
> [...]


Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.

The list of commits applied:
[1/1] platform/x86: portwell-ec: Move watchdog device under correct platform hierarchy
      commit: c8892c2a5b27d4026cda60409c393ba0d6c88df9

--
 i.


      reply	other threads:[~2025-06-17 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  7:48 [PATCH v2] platform/x86: portwell-ec: Move watchdog device under correct platform hierarchy Ivan Hu
2025-06-17 12:39 ` Ilpo Järvinen [this message]

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=175016396784.2117.17760069143731319818.b4-ty@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=hansg@kernel.org \
    --cc=ivan.hu@canonical.com \
    --cc=jesse.huang@portwell.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.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