From: Maninder Singh <maninder1.s@samsung.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "ardb@kernel.org" <ardb@kernel.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"nathan@kernel.org" <nathan@kernel.org>,
"nick.desaulniers+lkml@gmail.com"
<nick.desaulniers+lkml@gmail.com>,
"morbo@google.com" <morbo@google.com>,
"justinstitt@google.com" <justinstitt@google.com>,
Onkarnath <onkarnath.1@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
Rohit Thapliyal <r.thapliyal@samsung.com>
Subject: RE: [PATCH v2] arm: backtrace-clang: fix wrong sp usage for unwinding
Date: Tue, 11 Aug 2026 15:24:43 +0530 [thread overview]
Message-ID: <20260811095443epcms5p238a0ccbc4e42db5355fb6f181ccaeafd@epcms5p2> (raw)
In-Reply-To: <CGME20260805045522epcas5p39659721ef26a447b71e860c2990a60c0@epcms5p2>
Hi,
> Thanks for reviewing the patch, Actually I was not aware that ARM patches
> has to go through this way.
> Maybe that is the reason my last 2 bugfixes are also ignored from ARM side :)
> https://lkml.org/lkml/2026/4/27/265
>
> So I was checking the way and created account there to submit the patch.
> I will post the patch to suggested site today for further checking.
> https://www.arm.linux.org.uk/developer/patches/
uploaded:
9490/1 backtrace-clang: fix wrong sp usage for unwinding
https://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=9490/1
Thanks,
Maninder Singh
next parent reply other threads:[~2026-08-11 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260805045522epcas5p39659721ef26a447b71e860c2990a60c0@epcms5p2>
2026-08-11 9:54 ` Maninder Singh [this message]
[not found] <CGME20260805045522epcas5p39659721ef26a447b71e860c2990a60c0@epcas5p3.samsung.com>
2026-08-05 4:55 ` Maninder Singh
2026-08-06 17:03 ` Nick Desaulniers
[not found] ` <CGME20260805045522epcas5p39659721ef26a447b71e860c2990a60c0@epcms5p6>
2026-08-11 3:21 ` Maninder Singh
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=20260811095443epcms5p238a0ccbc4e42db5355fb6f181ccaeafd@epcms5p2 \
--to=maninder1.s@samsung.com \
--cc=ardb@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=onkarnath.1@samsung.com \
--cc=r.thapliyal@samsung.com \
/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
all inboxes | Powered by JetHome®