From: Sudeep Holla <sudeep.holla@kernel.org>
To: driver-core@lists.linux.dev
Cc: Sudeep Holla <sudeep.holla@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH v3 0/4] arch_topology: Bunch of error patch related fixes
Date: Mon, 9 Nov 2026 17:31:21 +0000 [thread overview]
Message-ID: <20261109173125.1734847-1-sudeep.holla@kernel.org> (raw)
Hi Greg,
Hopefully no more issues get reported by sashiko. It all started with
one issue[1] one patch and ended with 4 different issues so far. All of
them are related to error path handling.
v2->v3:
- Added fixes to couple of more issues pointed by Sashiko
- v2: https://lore.kernel.org/all/20261106164408.158337-1-sudeep.holla@kernel.org
v1->v2:
- Reset max_smt_thread_num to 1 on failure similar to parse_socket()
- Grouped below 2 in one series and posted them together
- v1: https://lore.kernel.org/all/20261104153413.2786066-1-sudeep.holla@kernel.org
- v1: https://lore.kernel.org/all/20261103093421.1283949-1-sudeep.holla@kernel.org
Regards,
Sudeep
[1] https://sashiko.dev/#/bug/linux-73adead8-21f3-470d-938c-b1f07a269a72
Sudeep Holla (4):
arch_topology: Reset SMT state when socket parsing fails
arch_topology: Free ACPI SMT entries on lookup failure
arch_topology: Reset SMT state when topology is unavailable
arch_topology: Free raw_capacity when topology parsing fails
drivers/base/arch_topology.c | 24 ++++++++++++++++++------
1 file changed, 18 insertions(+), 6 deletions(-)
--
2.43.0
next reply other threads:[~2026-11-09 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 17:31 Sudeep Holla [this message]
2026-11-09 17:31 ` [PATCH v3 1/4] arch_topology: Reset SMT state when socket parsing fails Sudeep Holla
2026-11-09 17:31 ` [PATCH v3 2/4] arch_topology: Free ACPI SMT entries on lookup failure Sudeep Holla
2026-11-09 17:31 ` [PATCH v3 3/4] arch_topology: Reset SMT state when topology is unavailable Sudeep Holla
2026-11-09 17:31 ` [PATCH v3 4/4] arch_topology: Free raw_capacity when topology parsing fails Sudeep Holla
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=20261109173125.1734847-1-sudeep.holla@kernel.org \
--to=sudeep.holla@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.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