netdev - Re: [PATCH iwl-next v3 0/3] ice:Support to dump PHY config, FEC

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 for Android: free password hash cracker in your pocket

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

Message-ID: <2fe273b9-dd6b-408c-bc69-e12c00b4141d@intel.com>
Date: Fri, 24 May 2024 14:11:25 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: Anil Samal <anil.samal@...el.com>, <intel-wired-lan@...ts.osuosl.org>
CC: <netdev@...r.kernel.org>, <leszek.pepiak@...el.com>,
	<przemyslaw.kitszel@...el.com>, <lukasz.czapnik@...el.com>,
	<anthony.l.nguyen@...el.com>
Subject: Re: [PATCH iwl-next v3 0/3] ice:Support to dump PHY config, FEC



On 5/24/2024 6:51 AM, Anil Samal wrote:
> Implementation to dump PHY configuration and FEC statistics to
> facilitate link level debugging of customer issues.  Implementation has
> two parts 
>   

What commit is this based off of? I believe we have slightly conflicting
work already queued in IWL next-queue, and the NIPA automation is unable
to apply this series for testing:

> [IWL-NIPA] Patch: https://patchwork.ozlabs.org/patch/1939088
> Pass: 1 Warn: 0 Fail: 1
> 
> Patch: https://patchwork.ozlabs.org/patch/1939088
> results path: results/408098/1939088
> 
> Test: apply
> Fail - Patch does not apply to next-queue
> 
> Test: tree_selection
> Okay - Clearly marked for next-queue

Normally, basing directly on net-next is fine. Unfortunately, I am
having trouble properly resolving the conflicts with the work on the
queue already.

If you could rebase this on top of dev-queue [1] that would be appreciated.

[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git/commit/?h=dev-queue