linux-kernel - Re: [PATCH] platform/x86: intel_pmc

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 08 Feb 2017 14:52:16 +0200
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Rajneesh Bhardwaj <rajneesh.bhardwaj@...el.com>,
        Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     kbuild test robot <lkp@...el.com>,
        Shanth Murthy <shanth.murthy@...el.com>, kbuild-all@...org,
        Platform Driver <platform-driver-x86@...r.kernel.org>,
        "dvhart@...radead.org" <dvhart@...radead.org>,
        Zha Qipeng <qipeng.zha@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] platform/x86: intel_pmc_ipc: read s0ix residency API

On Wed, 2017-02-08 at 17:32 +0530, Rajneesh Bhardwaj wrote:
> On Tue, Feb 07, 2017 at 12:19:10PM +0200, Andy Shevchenko wrote:
> > On Mon, Feb 6, 2017 at 8:31 PM, Rajneesh Bhardwaj
> > <rajneesh.bhardwaj@...el.com> wrote:
> > > On Mon, Feb 06, 2017 at 10:01:43PM +0800, kbuild test robot wrote:

> Andy, thanks for the fix. We had a look at the patch that was pushed
> to
> testing and think that still one issue exist when we compile with
> CONFIG_64BIT not set. Config attached.
> (linux-platform-drivers-
> x86.git/commit/c0baf79f459dbbdfe272dda58d5bcc9a2e585d7e) 
> 
> Error:
> drivers/built-in.o: In function `intel_pmc_s0ix_counter_read':
> (.text+0x7352b4): undefined reference to `__udivdi3'
> make[2]: *** [vmlinux] Error 1

Thanks for report, Darren already reported this yesterday.

> In addition to this, please share your thoughts on the below change
> for IPC
> driver.

Thanks, but that's wrong.
I know what is the issue and how to fix it. Will do it soon.

-- 
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy