From: Oleg Nesterov <oleg@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v3 1/1] pidfd: implement PIDFD_THREAD flag for pidfd_open()
Date: Thu, 1 Feb 2024 09:47:09 +0100 [thread overview]
Message-ID: <20240201084709.GA27850@redhat.com> (raw)
In-Reply-To: <202402011558.BUpYBZyG-lkp@intel.com>
I guess I do not really need to reply, but just in case...
On 02/01, kernel test robot wrote:
>
> >> kernel/fork.c:2201:70: warning: if statement has empty body [-Wempty-body]
> 2201 | if (!pid || !pid_has_task(pid, thread ? PIDTYPE_PID : PIDTYPE_TGID));
> | ^
> kernel/fork.c:2201:70: note: put the semicolon on a separate line to silence this warning
> 1 warning generated.
Yes, thank you dear Kernel Test Robot, this was already fixed
by Tycho.
Oleg.
prev parent reply other threads:[~2024-02-01 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240131132602.GA23641@redhat.com>
2024-02-01 7:23 ` [PATCH v3 1/1] pidfd: implement PIDFD_THREAD flag for pidfd_open() kernel test robot
2024-02-01 8:47 ` Oleg Nesterov [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=20240201084709.GA27850@redhat.com \
--to=oleg@redhat.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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