From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Amer Al Shanawany <amer.shanawany@gmail.com>,
Shuah Khan <shuah@kernel.org>,
Swarup Laxman Kotiaklapudi <swarupkotikalapudi@gmail.com>,
Hugh Dickins <hughd@google.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] selftests: proc: remove unreached code and fix build warning
Date: Fri, 7 Jun 2024 18:25:34 +0300 [thread overview]
Message-ID: <eb9b2d6e-91eb-4fdc-b352-b3d0c290da2f@p183> (raw)
In-Reply-To: <20240604202531.5d559ec4daed484a7a23592c@linux-foundation.org>
On Tue, Jun 04, 2024 at 08:25:31PM -0700, Andrew Morton wrote:
> On Mon, 3 Jun 2024 17:24:47 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> > On Mon, Jun 03, 2024 at 02:42:20PM +0200, Amer Al Shanawany wrote:
> > > fix the following warning:
> > > proc-empty-vm.c:385:17: warning: ignoring return value of ‘write’
> >
> > > --- a/tools/testing/selftests/proc/proc-empty-vm.c
> > > +++ b/tools/testing/selftests/proc/proc-empty-vm.c
> > > @@ -381,9 +381,6 @@ static int test_proc_pid_statm(pid_t pid)
> >
> > > - if (0) {
> > > - write(1, buf, rv);
> > > - }
> >
> > no thanks
>
> Why not?
>
> Why does that code exist anyway? It at least needs a comment.
OK, whatever.
If test fails, it better record buggy output somewhere (to coredump or to terminal).
next prev parent reply other threads:[~2024-06-07 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202404010211.ygidvMwa-lkp@intel.com>
2024-06-03 12:42 ` [PATCH] selftests: proc: remove unreached code and fix build warning Amer Al Shanawany
2024-06-03 14:24 ` Alexey Dobriyan
2024-06-05 3:25 ` Andrew Morton
2024-06-07 15:25 ` Alexey Dobriyan [this message]
2024-06-11 15:04 ` 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=eb9b2d6e-91eb-4fdc-b352-b3d0c290da2f@p183 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=amer.shanawany@gmail.com \
--cc=hughd@google.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=shuah@kernel.org \
--cc=swarupkotikalapudi@gmail.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;
as well as URLs for NNTP newsgroup(s).