Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: "Marek Behún" <kabel@kernel.org>
Cc: Arnd Bergmann <arnd@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	kernel test robot <lkp@intel.com>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] platform: cznic: fix function parameter names
Date: Wed, 26 Mar 2025 09:23:55 -0700	[thread overview]
Message-ID: <20250326162355.GA2072652@ax162> (raw)
In-Reply-To: <l77cp7hlskzkauoohviwonal53upcyc74j7x57ycn7sdfkmu4f@fsm4tv2lbtn6>

On Wed, Mar 26, 2025 at 10:38:47AM +0100, Marek Behún wrote:
> > 
> > Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> > 
> > You will be taking this I assume?
> 
> Arnd already took it into for-next:
>   https://web.git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/log/?h=for-next

Ah odd, it just showed up in -next even though it was applied a few days
ago:

$ git log --oneline next-20250325 -- drivers/platform/cznic/turris-signing-key.c
0b28b7080ef5 platform: cznic: Add keyctl helpers for Turris platform

$ git log --oneline next-20250326 -- drivers/platform/cznic/turris-signing-key.c
eece12237a13 platform: cznic: fix function parameter names
0b28b7080ef5 platform: cznic: Add keyctl helpers for Turris platform

Glad that it is resolved now though.

Cheers,
Nathan

  reply	other threads:[~2025-03-26 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21  8:53 [PATCH] platform: cznic: fix function parameter names Arnd Bergmann
2025-03-25 15:59 ` Nathan Chancellor
2025-03-26  9:38   ` Marek Behún
2025-03-26 16:23     ` Nathan Chancellor [this message]
2025-03-26 16:28       ` Arnd Bergmann

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=20250326162355.GA2072652@ax162 \
    --to=nathan@kernel.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=justinstitt@google.com \
    --cc=kabel@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --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