From: sashiko-bot@kernel.org
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Alexander Gordeev" <agordeev@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 2/4] ORC: pull out module handling from x86/loongarch
Date: Thu, 24 Sep 2026 12:49:28 +0000 [thread overview]
Message-ID: <20260924124929.67CC41F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924144039.1f625ed6f732.Ief8583cee373b18ea2151118373ff3d8ab73ac60@changeid>
> From: Johannes Berg <johannes.berg@intel.com>
>
> The x86 and loongarch code for ORC unwinder are just
> copied code, and I don't want to add another copy for
> UML. Pull out the common module section handling into
> the regular module code to reduce duplication.
>
> I used the x86 version, but loongarch is identical
> except for variable declaration order.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260924124039.1621965-6-johannes@sipsolutions.net?part=2
next prev parent reply other threads:[~2026-09-24 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 12:35 [PATCH 0/4] ORC unwinder cleanup & UML support Johannes Berg
2026-09-24 12:35 ` [PATCH 1/4] s390: remove unwind_module_init() Johannes Berg
2026-09-24 12:43 ` sashiko-bot
2026-09-24 12:48 ` Heiko Carstens
2026-09-24 12:35 ` [PATCH 2/4] ORC: pull out module handling from x86/loongarch Johannes Berg
2026-09-24 12:49 ` sashiko-bot [this message]
2026-09-24 12:35 ` [PATCH 3/4] ORC: unify orc_hash.h generation Johannes Berg
2026-09-24 12:48 ` sashiko-bot
2026-09-24 12:35 ` [PATCH 4/4] um: ORC unwinder support Johannes Berg
2026-09-24 12:52 ` sashiko-bot
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=20260924124929.67CC41F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.