From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
linux-acpi@vger.kernel.org, "Len Brown" <lenb@kernel.org>,
"Daniel Scally" <dan.scally@ideasonboard.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org
Subject: [PATCH v3 0/3] Fix static analyser and compiler warnings in int3472
Date: Tue, 25 Aug 2026 23:35:50 +0300 [thread overview]
Message-ID: <20260825203553.3725132-1-sakari.ailus@linux.intel.com> (raw)
Hi folks,
The two first patches address smatch and compiler warnings in int3472. The
third patch clean up GPIO parsing in the int3472 driver.
since v2:
- Drop the __free(ACPI_FREE) change.
- Move ACPI_FREE() earlier in the function and save the object's integer
value into a local variable.
- Fix return values -- 0 was returned by v2 in some cases where 1 was the
right value.
Sakari Ailus (3):
platform/x86: int3472: Address Coccinelle warning on an error print
platform/x86: int3472: Fix uninitialised variable warning
platform/x86: int3472: Clean up GPIO parsing
drivers/platform/x86/intel/int3472/discrete.c | 51 +++++++++----------
drivers/platform/x86/intel/int3472/tps68470.c | 2 +-
2 files changed, 25 insertions(+), 28 deletions(-)
base-commit: 56c29fa3ee666197516a231e75aed789ae9c530d
--
2.47.3
next reply other threads:[~2026-08-25 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 20:35 Sakari Ailus [this message]
2026-08-25 20:35 ` [PATCH v3 1/3] platform/x86: int3472: Address Coccinelle warning on an error print Sakari Ailus
2026-08-25 21:01 ` Ricardo Ribalda Delgado
2026-08-27 8:25 ` Dan Scally
2026-08-25 20:35 ` [PATCH v3 2/3] platform/x86: int3472: Fix uninitialised variable warning Sakari Ailus
2026-08-25 21:04 ` Ricardo Ribalda Delgado
2026-08-26 7:04 ` Sakari Ailus
2026-08-27 11:16 ` Dan Scally
2026-08-25 20:35 ` [PATCH v3 3/3] platform/x86: int3472: Clean up GPIO parsing Sakari Ailus
2026-08-27 11:39 ` Dan Scally
2026-08-26 10:41 ` [PATCH v3 0/3] Fix static analyser and compiler warnings in int3472 Rafael J. Wysocki (Intel)
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=20260825203553.3725132-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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