From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Dave Penkler <dpenkler@gmail.com>,
linux-staging@lists.linux.dev, llvm@lists.linux.dev,
patches@lists.linux.dev
Subject: Re: [PATCH] staging: gpid: fmh: Drop residue from fmh_gpid_fifo_read_countable()
Date: Wed, 16 Oct 2024 09:59:31 +0200 [thread overview]
Message-ID: <2024101607-unmovable-serving-6a0d@gregkh> (raw)
In-Reply-To: <20241015-staging-gpib-fmh-fix-residue-used-uninitialized-v1-1-23ef05b099da@kernel.org>
On Tue, Oct 15, 2024 at 01:09:02PM -0700, Nathan Chancellor wrote:
> Clang warns (or errors with CONFIG_WERROR=y):
<snip>
Nit, the subject should have had "gpib" not "gpid". I've fixed it up
when applying, thanks for the fix!
greg k-h
next prev parent reply other threads:[~2024-10-16 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 20:09 [PATCH] staging: gpid: fmh: Drop residue from fmh_gpid_fifo_read_countable() Nathan Chancellor
2024-10-16 7:59 ` Greg Kroah-Hartman [this message]
2024-10-16 15:19 ` Nathan Chancellor
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=2024101607-unmovable-serving-6a0d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dpenkler@gmail.com \
--cc=linux-staging@lists.linux.dev \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=patches@lists.linux.dev \
/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