From: kbuild test robot <lkp@intel.com>
To: Eugene Syromiatnikov <esyr@redhat.com>
Cc: kbuild-all@01.org, John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uapi, posix-timers: provide clockid-related macros and functions to UAPI
Date: Sun, 22 Sep 2019 15:56:16 +0800 [thread overview]
Message-ID: <20190922075616.GJ13569@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20190920162003.GA31301@asgard.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]
Hi Eugene,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3 next-20190920]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Eugene-Syromiatnikov/uapi-posix-timers-provide-clockid-related-macros-and-functions-to-UAPI/20190921-051356
config: i386-randconfig-a003-201937 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
:::::: branch date: 6 hours ago
:::::: commit date: 6 hours ago
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from ./usr/include/linux/timex.h:56:0,
from <command-line>:32:
>> ./usr/include/linux/time.h:98:19: error: unknown type name 'clockid_t'
static __inline__ clockid_t make_process_cpuclock(const unsigned int pid,
^~~~~~~~~
./usr/include/linux/time.h:99:9: error: unknown type name 'clockid_t'
const clockid_t clock)
^~~~~~~~~
./usr/include/linux/time.h:103:19: error: unknown type name 'clockid_t'
static __inline__ clockid_t make_thread_cpuclock(const unsigned int tid,
^~~~~~~~~
./usr/include/linux/time.h:104:9: error: unknown type name 'clockid_t'
const clockid_t clock)
^~~~~~~~~
./usr/include/linux/time.h:109:19: error: unknown type name 'clockid_t'
static __inline__ clockid_t fd_to_clockid(const int fd)
^~~~~~~~~
./usr/include/linux/time.h:114:43: error: unknown type name 'clockid_t'
static __inline__ int clockid_to_fd(const clockid_t clk)
^~~~~~~~~
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30645 bytes --]
prev parent reply other threads:[~2019-09-22 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 16:20 [PATCH] uapi, posix-timers: provide clockid-related macros and functions to UAPI Eugene Syromiatnikov
2019-09-22 7:56 ` kbuild test robot [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=20190922075616.GJ13569@xsang-OptiPlex-9020 \
--to=lkp@intel.com \
--cc=bigeasy@linutronix.de \
--cc=ebiederm@xmission.com \
--cc=esyr@redhat.com \
--cc=frederic@kernel.org \
--cc=john.stultz@linaro.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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).