From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Wei Liu <wei.liu@kernel.org>
Cc: eahariha@linux.microsoft.com, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev,
Michael Kelley <mhklinux@outlook.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [hyperv:hyperv-fixes 5/11] drivers/hv/vmbus_drv.c:2510:45: error: call to undeclared function 'secs_to_jiffies'; ISO C99 and later do not support implicit function declarations
Date: Mon, 9 Dec 2024 08:52:27 -0800 [thread overview]
Message-ID: <fba68cce-2445-4a1d-a609-b6308a62c1b3@linux.microsoft.com> (raw)
In-Reply-To: <202412091658.m9g4L9gw-lkp@intel.com>
On 12/8/2024 9:50 PM, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git hyperv-fixes
> head: b8ea8cd0fbd358feee3e9172c5ef8afd671e0d11
> commit: eced6df67f6b76889e80ded109a73ca5fac1e5cd [5/11] drivers: hv: Convert open-coded timeouts to secs_to_jiffies()
> config: i386-buildonly-randconfig-004-20241209 (https://download.01.org/0day-ci/archive/20241209/202412091658.m9g4L9gw-lkp@intel.com/config)
> compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241209/202412091658.m9g4L9gw-lkp@intel.com/reproduce)
>
Hi Wei,
It appears hyperv-fixes needs to be rebased on 6.13-rc1 to provide
secs_to_jiffies() from commit b35108a51cf7bab58d7eace1267d7965978bcdb8
(jiffies: Define secs_to_jiffies()). I suppose you'll do that before
sending the PR to Linus.
Thanks,
Easwar
next prev parent reply other threads:[~2024-12-09 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 5:50 [hyperv:hyperv-fixes 5/11] drivers/hv/vmbus_drv.c:2510:45: error: call to undeclared function 'secs_to_jiffies'; ISO C99 and later do not support implicit function declarations kernel test robot
2024-12-09 16:52 ` Easwar Hariharan [this message]
2024-12-09 18:38 ` Wei Liu
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=fba68cce-2445-4a1d-a609-b6308a62c1b3@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mhklinux@outlook.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wei.liu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.