From: Nathan Chancellor <nathan@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: justinstitt@google.com, linux-media@vger.kernel.org,
llvm@lists.linux.dev, mchehab@kernel.org, morbo@google.com,
ndesaulniers@google.com, patches@lists.linux.dev,
stable@vger.kernel.org
Subject: Re: [PATCH] media: mxl5xx: Move xpt structures off stack
Date: Mon, 12 Feb 2024 16:27:57 -0700 [thread overview]
Message-ID: <20240212232757.GA3221859@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20240210162604.342349-1-ojeda@kernel.org>
On Sat, Feb 10, 2024 at 05:26:04PM +0100, Miguel Ojeda wrote:
> > On Thu, 11 Jan 2024 17:40:36 -0700 Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > Closes: https://github.com/ClangBuiltLinux/linux/issues/1977
>
> The next one: 1978 :)
This is probably the third link I have messed up in the past couple of
weeks :/ Mauro, do you want a v2 for these two minor issues or can you
fix them up during application?
> > of the stackvia 'static const', which is a better location for these
>
> Nit: space.
>
> Built-tested for loongarch64:
>
> Reviewed-by: Miguel Ojeda <ojeda@kernel.org>
> Tested-by: Miguel Ojeda <ojeda@kernel.org>
>
> With this applied, I have a `WERROR`-clean `defconfig` build with a Rust-enabled
> kernel using LLVM 18 (using LLVM-provided apt pre-releases).
Thanks for taking a look, this is great to hear!
Cheers,
Nathan
next prev parent reply other threads:[~2024-02-12 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 0:40 [PATCH] media: mxl5xx: Move xpt structures off stack Nathan Chancellor
2024-02-10 16:26 ` Miguel Ojeda
2024-02-12 23:27 ` Nathan Chancellor [this message]
2024-02-13 20:37 ` Miguel Ojeda
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=20240212232757.GA3221859@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-media@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=morbo@google.com \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).