From: Nathan Chancellor <nathan@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Guenter Roeck <linux@roeck-us.net>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
clang-built-linux <llvm@lists.linux.dev>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, Nick Desaulniers <ndesaulniers@google.com>,
Sven Volkinsfeld <thyrc@gmx.net>,
Daniel Kolesa <daniel@octaforge.org>,
x86@kernel.org
Subject: Re: [PATCH 6.1 000/127] 6.1.45-rc1 review
Date: Mon, 14 Aug 2023 09:52:46 -0700 [thread overview]
Message-ID: <20230814165246.GA911700@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20230813110254.GDZNi4XhHjY4xlNdBJ@fat_crate.local>
On Sun, Aug 13, 2023 at 01:02:54PM +0200, Borislav Petkov wrote:
> On Thu, Aug 10, 2023 at 09:13:39PM -0700, Nathan Chancellor wrote:
> > 1911 is still being investigated (some additional eyes on it would not
> > hurt).
>
> I'm hoping that we can take this one:
>
> https://lore.kernel.org/r/20230809072200.543939260@infradead.org
>
> which should resolve this issue, right?
Yes, it does, as least for mainline and 6.4. The backport to 6.1 seems
hairy (due to a lack of call depth tracking me thinks). It may be worth
taking Nick's change there for simplicity's sake but I'll let y'all make
that decision.
Cheers,
Nathan
prev parent reply other threads:[~2023-08-14 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230809103636.615294317@linuxfoundation.org>
2023-08-11 3:22 ` [PATCH 6.1 000/127] 6.1.45-rc1 review Naresh Kamboju
2023-08-11 3:36 ` Nathan Chancellor
2023-08-11 3:41 ` Guenter Roeck
2023-08-11 4:13 ` Nathan Chancellor
2023-08-13 11:02 ` Borislav Petkov
2023-08-14 16:52 ` Nathan Chancellor [this message]
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=20230814165246.GA911700@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=conor@kernel.org \
--cc=daniel@octaforge.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=ndesaulniers@google.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=thyrc@gmx.net \
--cc=torvalds@linux-foundation.org \
--cc=x86@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