linux-kernel - Re: [PATCH v1 2/2] i2c: mlxbf: Use HZ_PER

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aWbbVUbMkKAAV+s6@rli9-mobl>
Date: Wed, 14 Jan 2026 07:55:01 +0800
From: Philip Li <philip.li@...el.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
CC: kernel test robot <lkp@...el.com>, <linux-i2c@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <oe-kbuild-all@...ts.linux.dev>, "Khalil
 Blaiech" <kblaiech@...dia.com>, Asmaa Mnebhi <asmaa@...dia.com>, Andi Shyti
	<andi.shyti@...nel.org>
Subject: Re: [PATCH v1 2/2] i2c: mlxbf: Use HZ_PER_KHZ in the driver

On Tue, Jan 13, 2026 at 10:42:41PM +0200, Andy Shevchenko wrote:
> On Tue, Jan 13, 2026 at 09:48:12PM +0800, Philip Li wrote:
> > 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.
> 
> No problem, can you remind the syntax on how I can mark the series that
> LKP knows the dependency on another series (which is available only in
> the mailing list)? I assume it needs message-id to the email thread?

Currently to get dependency of another series is not supported yet, and
for now, we can only support the usage of '--base' option as documented
in [1] to avoid applying the patchset to wrong base.

Your suggestion is very helpful, probably we can check something like
base-message-id: (similar to base-commit:) to retrieve the dependency.

[1] https://git-scm.com/docs/git-format-patch#_base_tree_information

> 
> -- 
> With Best Regards,
> Andy Shevchenko
> 
>