From: Philip Li <philip.li@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: kernel test robot <lkp@intel.com>, <linux-i2c@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <oe-kbuild-all@lists.linux.dev>,
"Khalil Blaiech" <kblaiech@nvidia.com>,
Asmaa Mnebhi <asmaa@nvidia.com>,
Andi Shyti <andi.shyti@kernel.org>
Subject: Re: [PATCH v1 2/2] i2c: mlxbf: Use HZ_PER_KHZ in the driver
Date: Tue, 13 Jan 2026 21:48:12 +0800 [thread overview]
Message-ID: <aWZNHKeXFMPMG9q1@rli9-mobl> (raw)
In-Reply-To: <aWVbYYusNh_q_91o@smile.fi.intel.com>
On Mon, Jan 12, 2026 at 10:36:49PM +0200, Andy Shevchenko wrote:
> On Tue, Jan 13, 2026 at 04:33:04AM +0800, kernel test robot wrote:
> > Hi Andy,
> >
> > kernel test robot noticed the following build errors:
>
> Ah, okay, this needs to be based on the series that adds HZ_PER_GHZ as it
> provides the needed header inclusion.
Thanks for the info, and sorry for the false report.
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
>
next prev parent reply other threads:[~2026-01-13 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 13:55 [PATCH v1 0/2] i2c: mlxbf: A couple of cleanups Andy Shevchenko
2026-01-12 13:55 ` [PATCH v1 1/2] i2c: mlxbf: Remove unused bus speed definitions Andy Shevchenko
2026-01-12 13:55 ` [PATCH v1 2/2] i2c: mlxbf: Use HZ_PER_KHZ in the driver Andy Shevchenko
2026-01-12 20:33 ` kernel test robot
2026-01-12 20:36 ` Andy Shevchenko
2026-01-13 7:30 ` Andy Shevchenko
2026-01-13 13:48 ` Philip Li [this message]
2026-01-13 20:42 ` Andy Shevchenko
2026-01-13 23:55 ` Philip Li
2026-01-14 7:36 ` [PATCH v1 0/2] i2c: mlxbf: A couple of cleanups Andi Shyti
2026-01-14 8:24 ` Andy Shevchenko
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=aWZNHKeXFMPMG9q1@rli9-mobl \
--to=philip.li@intel.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=asmaa@nvidia.com \
--cc=kblaiech@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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