From: "Brian Cain" <bcain@codeaurora.org>
To: "'Nathan Chancellor'" <nathan@kernel.org>,
"'Andrew Morton'" <akpm@linux-foundation.org>
Cc: "'Nick Desaulniers'" <ndesaulniers@google.com>,
<linux-hexagon@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<clang-built-linux@googlegroups.com>
Subject: RE: [PATCH 0/3] hexagon: Fix build error with CONFIG_STACKDEPOT and select CONFIG_ARCH_WANT_LD_ORPHAN_WARN
Date: Thu, 3 Jun 2021 11:59:43 -0500 [thread overview]
Message-ID: <09a301d75899$daf244f0$90d6ced0$@codeaurora.org> (raw)
In-Reply-To: <0f3ac242-d187-57b5-e715-ea25933dbd52@kernel.org>
> -----Original Message-----
> From: Nathan Chancellor <nathan@kernel.org>
...
> On 5/20/2021 6:12 PM, Nathan Chancellor wrote:
> > Hi all,
...
> Brian, did you have any comments on this series? ARCH=hexagon defconfig
> is currently broken in -next, it would be a real shame if this continued
> to regress after you just got Hexagon building in mainline. These
> patches seem like they would be worthy of a 5.13 pull request.
I have started the internal review process to get these queued up in my tree. But I don't know if I would have it in time for 5.13.
> Otherwise, Andrew could pick them up with your ack and stick them in
> front of "mm/slub: use stackdepot to save stack trace in objects" so
> that there is no build regression.
Of course: I'll send my ack for the sake of keeping the build green.
-Brian
next prev parent reply other threads:[~2021-06-03 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 1:12 [PATCH 0/3] hexagon: Fix build error with CONFIG_STACKDEPOT and select CONFIG_ARCH_WANT_LD_ORPHAN_WARN Nathan Chancellor
2021-05-21 1:12 ` [PATCH 1/3] hexagon: Handle {,SOFT}IRQENTRY_TEXT in linker script Nathan Chancellor
2021-06-01 19:16 ` Nick Desaulniers
2021-06-03 16:59 ` Brian Cain
2021-05-21 1:12 ` [PATCH 2/3] hexagon: Use common DISCARDS macro Nathan Chancellor
2021-06-01 19:18 ` Nick Desaulniers
2021-06-03 16:59 ` Brian Cain
2021-05-21 1:12 ` [PATCH 3/3] hexagon: Select ARCH_WANT_LD_ORPHAN_WARN Nathan Chancellor
2021-06-01 19:20 ` Nick Desaulniers
2021-06-03 16:59 ` Brian Cain
2021-06-03 1:17 ` [PATCH 0/3] hexagon: Fix build error with CONFIG_STACKDEPOT and select CONFIG_ARCH_WANT_LD_ORPHAN_WARN Nathan Chancellor
2021-06-03 16:59 ` Brian Cain [this message]
2021-06-15 17:25 ` Nathan Chancellor
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='09a301d75899$daf244f0$90d6ced0$@codeaurora.org' \
--to=bcain@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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;
as well as URLs for NNTP newsgroup(s).