From: Kees Cook <kees@kernel.org>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: bhelgaas@google.com, ojeda@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, arnd@arndb.de,
dan.carpenter@linaro.org, benjamin.copeland@linaro.org,
Linux Kernel Functional Testing <lkft@linaro.org>
Subject: Re: [PATCH] drivers/pci: Fix FIELD_PREP compilation error with gcc-8
Date: Thu, 4 Sep 2025 22:31:14 -0700 [thread overview]
Message-ID: <202509042228.A2332756A5@keescook> (raw)
In-Reply-To: <202509032125.F41E71AF19@keescook>
On Wed, Sep 03, 2025 at 09:29:40PM -0700, Kees Cook wrote:
> Thanks for examining this! It seems rather alarming -- why did it
> work before?
I've proposed an alternative:
https://lore.kernel.org/lkml/20250905052836.work.425-kees@kernel.org/
--
Kees Cook
next prev parent reply other threads:[~2025-09-05 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 10:12 [PATCH] drivers/pci: Fix FIELD_PREP compilation error with gcc-8 Anders Roxell
2025-09-04 4:29 ` Kees Cook
2025-09-05 5:31 ` Kees Cook [this message]
2025-09-06 13:12 ` David Laight
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=202509042228.A2332756A5@keescook \
--to=kees@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=bhelgaas@google.com \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkft@linaro.org \
--cc=ojeda@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