From: Andy Shevchenko <andy@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/4] platform/x86: int3472: Check for adev == NULL
Date: Thu, 28 Nov 2024 17:51:49 +0200 [thread overview]
Message-ID: <Z0iRlZPFYItHIV7_@smile.fi.intel.com> (raw)
In-Reply-To: <20241128154212.6216-1-hdegoede@redhat.com>
On Thu, Nov 28, 2024 at 04:42:09PM +0100, Hans de Goede wrote:
> Not all devices have an ACPI companion fwnode, so adev might be NULL. This
> can e.g. (theoretically) happen when a user manually binds one of
> the int3472 drivers to another i2c/platform device through sysfs.
>
> Add a check for adev not being set and return -ENODEV in that case.
But what kind of "bad thing" can happen in such cases?
If none, why this change?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-11-28 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 15:42 [PATCH 1/4] platform/x86: int3472: Check for adev == NULL Hans de Goede
2024-11-28 15:42 ` [PATCH 2/4] platform/x86: int3472: Drop "pin number mismatch" messages Hans de Goede
2024-11-28 15:52 ` Andy Shevchenko
2024-12-04 17:36 ` Hans de Goede
2024-12-04 18:23 ` Andy Shevchenko
2024-11-28 15:42 ` [PATCH 3/4] platform/x86: int3472: Fix skl_int3472_handle_gpio_resources() return value Hans de Goede
2024-11-28 15:53 ` Andy Shevchenko
2024-12-04 17:37 ` Hans de Goede
2024-11-28 15:42 ` [PATCH 4/4] platform/x86: int3472: Debug log the sensor name Hans de Goede
2024-11-28 15:51 ` Andy Shevchenko [this message]
2024-12-04 17:40 ` [PATCH 1/4] platform/x86: int3472: Check for adev == NULL Hans de Goede
2024-12-04 19:15 ` Andy Shevchenko
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=Z0iRlZPFYItHIV7_@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--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