From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jann Horn" <jannh@google.com>
Cc: "Jens Wiklander" <jens.wiklander@linaro.org>,
arm <arm@kernel.org>,
soc@kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
op-tee@lists.trustedfirmware.org
Subject: Re: [GIT PULL] TEE updates for 6.16
Date: Sat, 10 May 2025 11:10:10 +0200 [thread overview]
Message-ID: <a877f411-f6df-45dd-9cf2-351d785db4c2@app.fastmail.com> (raw)
In-Reply-To: <CAG48ez3JEg11GZTzmSHeXEDVz9vN68vWjTH+2sq_6+8eK0zkig@mail.gmail.com>
On Fri, May 9, 2025, at 23:22, Jann Horn wrote:
> On Fri, May 9, 2025 at 11:14 PM Arnd Bergmann <arnd@arndb.de> wrote:
>> The second patch looks like it should be a bugfix for 6.15 instead,
>> any reason to have it only in 6.16?
>
> FWIW, it's more of a cleanup than a real bugfix; there is an unsigned
> integer wraparound, but if that occurs, we're guaranteed to hit a
> memory allocation bailout pretty much immediately afterwards. So I
> think putting it in 6.16 is reasonable.
Ok, I see. Merged now.
Arnd
prev parent reply other threads:[~2025-05-10 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 6:51 Jens Wiklander
2025-05-09 21:14 ` Arnd Bergmann
2025-05-09 21:22 ` Jann Horn
2025-05-10 9:10 ` Arnd Bergmann [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=a877f411-f6df-45dd-9cf2-351d785db4c2@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=jannh@google.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=soc@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
all inboxes | Powered by JetHome®