From: Sargun Dhillon <sargun@sargun.me>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, LKML <linux-kernel@vger.kernel.org>,
"Linux Containers" <containers@lists.linux-foundation.org>,
"Linux API" <linux-api@vger.kernel.org>,
"Linux FS-devel Mailing List" <linux-fsdevel@vger.kernel.org>,
"Tycho Andersen" <tycho@tycho.ws>, "Jann Horn" <jannh@google.com>,
"Aleksa Sarai" <cyphar@cyphar.com>,
"Christian Brauner" <christian.brauner@ubuntu.com>,
"Oleg Nesterov" <oleg@redhat.com>,
"Andy Lutomirski" <luto@amacapital.net>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Gian-Carlo Pascutto" <gpascutto@mozilla.com>,
"Emilio Cobos Álvarez" <ealvarez@mozilla.com>,
"Florian Weimer" <fweimer@redhat.com>,
"Jed Davis" <jld@mozilla.com>, "Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH v7 2/3] pid: Introduce pidfd_getfd syscall
Date: Thu, 26 Dec 2019 20:35:00 -0500 [thread overview]
Message-ID: <CAMp4zn94deUbkXBrnX=Omw9-FmoZDANApqYUVsaV+VsXCX4Q-w@mail.gmail.com> (raw)
In-Reply-To: <201912270545.TQnRs9kG%lkp@intel.com>
On Thu, Dec 26, 2019 at 5:20 PM kbuild test robot <lkp@intel.com> wrote:
>
> Hi Sargun,
>
> Thank you for the patch! Yet something to improve:
>
> All errors (new ones prefixed by >>):
>
> arch/alpha/kernel/systbls.o: In function `sys_call_table':
> >> (.data+0x1120): undefined reference to `sys_pidfd'
This is a small typo. I'll fix this in the next respin.
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
next prev parent reply other threads:[~2019-12-27 1:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 18:03 [PATCH v7 2/3] pid: Introduce pidfd_getfd syscall Sargun Dhillon
2019-12-26 22:20 ` kbuild test robot
2019-12-27 1:35 ` Sargun Dhillon [this message]
2019-12-28 10:11 ` Christian Brauner
2019-12-28 13:03 ` Sargun Dhillon
2019-12-29 17:32 ` Christian Brauner
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='CAMp4zn94deUbkXBrnX=Omw9-FmoZDANApqYUVsaV+VsXCX4Q-w@mail.gmail.com' \
--to=sargun@sargun.me \
--cc=arnd@arndb.de \
--cc=christian.brauner@ubuntu.com \
--cc=containers@lists.linux-foundation.org \
--cc=cyphar@cyphar.com \
--cc=ealvarez@mozilla.com \
--cc=fweimer@redhat.com \
--cc=gpascutto@mozilla.com \
--cc=jannh@google.com \
--cc=jld@mozilla.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=tycho@tycho.ws \
--cc=viro@zeniv.linux.org.uk \
/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).