From: Dan Carpenter <dan.carpenter@linaro.org>
To: root <info@ljfogelstrom.se>
Cc: shuah@kernel.org, skhan@linuxfoundation.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] selftests/filesystems/mount-notify: fix unused result compiler warning
Date: Mon, 2 Feb 2026 12:05:59 +0300 [thread overview]
Message-ID: <aYBo9xj1A8Jjlmjw@stanley.mountain> (raw)
In-Reply-To: <20260201144416.1637814-1-root@ljfogelstrom.se>
On Sun, Feb 01, 2026 at 02:43:17PM +0000, root wrote:
> From: LJ Fogelstrom <info@ljfogelstrom.se>
>
> Compiling with GCC emits Wwarn-unused-result for these two
> statements, so they are now wrapped in an assert similar to the rest of
> the code.
>
> (Apologies for sending this twice; I am new and missed to include the
> maintainers the first time)
>
Don't include this kind of thing in the commit message.
To be honest, I would just ignore the warning. I think the code looks
worse at the end.
regards,
dan carpenter
prev parent reply other threads:[~2026-02-02 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 14:43 [PATCH] selftests/filesystems/mount-notify: fix unused result compiler warning root
2026-02-02 9:05 ` Dan Carpenter [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=aYBo9xj1A8Jjlmjw@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=info@ljfogelstrom.se \
--cc=kernel-janitors@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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