From: Shuah Khan <skhan@linuxfoundation.org>
To: Abhinav Jain <jain.abhinav177@gmail.com>, shuah@kernel.org
Cc: javier.carrasco.cruz@gmail.com,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org, brauner@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: filesystems: fix warn_unused_result build warnings
Date: Tue, 3 Sep 2024 11:45:38 -0600 [thread overview]
Message-ID: <405c28dd-bf6d-4f17-92c4-182808182899@linuxfoundation.org> (raw)
In-Reply-To: <5fd97d54-fa64-4c03-865f-961ed4596a6e@linuxfoundation.org>
On 8/16/24 07:11, Shuah Khan wrote:
> On 8/10/24 07:53, Abhinav Jain wrote:
>> Add return value checks for read & write calls in test_listmount_ns
>> function. This patch resolves below compilation warnings:
>>
>> ```
>> statmount_test_ns.c: In function ‘test_listmount_ns’:
>>
>> statmount_test_ns.c:322:17: warning: ignoring return value of ‘write’
>> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>>
>> statmount_test_ns.c:323:17: warning: ignoring return value of ‘read’
>> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>> ```
>>
>> Signed-off-by: Abhinav Jain <jain.abhinav177@gmail.com>
>> ---
> Hi Christian,
>
> Let me know if it is okay to take this patch through kselftest tree.
> The change looks good to me.
>
> thanks,
> -- Shuah
Thank you for the patch.
Applied to linux-kselftest next for Linux 6.12-rc1
thanks,
-- Shuah
next prev parent reply other threads:[~2024-09-03 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 13:53 [PATCH] selftests: filesystems: fix warn_unused_result build warnings Abhinav Jain
2024-08-16 13:11 ` Shuah Khan
2024-09-03 17:45 ` Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-17 18:49 Amer Al Shanawany
2024-04-19 16:41 ` Muhammad Usama Anjum
2024-05-04 17:17 ` Amer Al Shanawany
2024-06-03 11:17 ` Amer Al Shanawany
2024-06-11 15:23 ` Shuah Khan
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=405c28dd-bf6d-4f17-92c4-182808182899@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=jain.abhinav177@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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