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]
Message-ID: <06719894-7acd-9bfb-bdf7-4aa9eba21f2f@collabora.com>
Date:   Tue, 28 Nov 2023 13:17:17 +0530
From:   Vignesh Raman <vignesh.raman@...labora.com>
To:     Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
        jani.nikula@...ux.intel.com
Cc:     intel-gfx@...ts.freedesktop.org, helen.koike@...labora.com,
        daniels@...labora.com, dri-devel@...ts.freedesktop.org,
        linux-kernel@...r.kernel.org, david.e.box@...ux.intel.com,
        swati2.sharma@...el.com
Subject: Re: [PATCH] PCI: qcom: Fix compile error


On 28/11/23 12:21, Manivannan Sadhasivam wrote:
> On Tue, Nov 28, 2023 at 11:44:26AM +0530, Vignesh Raman wrote:
>> Hi Mani,
>>
>> On 28/11/23 10:44, Manivannan Sadhasivam wrote:
>>> On Tue, Nov 28, 2023 at 09:50:26AM +0530, Vignesh Raman wrote:
>>>> Commit a2458d8f618a ("PCI/ASPM: pci_enable_link_state: Add argument
>>>> to acquire bus lock") has added an argument to acquire bus lock
>>>> in pci_enable_link_state, but qcom_pcie_enable_aspm calls it
>>>> without this argument, resulting in below build error.
>>>>
>>>
>>> Where do you see this error? That patch is not even merged. Looks like you are
>>> sending the patch against some downstream tree.
>>
>> I got this error with drm-tip - git://anongit.freedesktop.org/drm-tip
>>
>> This commit is merged in drm-intel/topic/core-for-CI -
>> https://cgit.freedesktop.org/drm-intel/log/?h=topic/core-for-CI
>>
> 
> Okay. Since this patch is just for CI, please do not CC linux-pci as it causes
> confusion.

Sure, thank you.

Jani, is this fix required for topic/core-for-CI ?

Regards,
Vignesh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ