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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <DS7PR11MB6037D67A617D1C6FC667EEF799C42@DS7PR11MB6037.namprd11.prod.outlook.com>
Date: Sat, 8 Jun 2024 18:14:25 +0000
From: "Samal, Anil" <anil.samal@...el.com>
To: "Keller, Jacob E" <jacob.e.keller@...el.com>,
	"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "Pepiak, Leszek"
	<leszek.pepiak@...el.com>, "Kitszel, Przemyslaw"
	<przemyslaw.kitszel@...el.com>, "Czapnik, Lukasz" <lukasz.czapnik@...el.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>
Subject: RE: [PATCH iwl-next v3 0/3] ice:Support to dump PHY config, FEC

Hi Jacob, 
Can you please help me with the branch name that I should rebase? 
Last time I rebased to "dev-queue" branch of "git clone git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git". 

Let me know, if I should use a different branch for rebasing. 

Thanks
Anil 

-----Original Message-----
From: Keller, Jacob E <jacob.e.keller@...el.com> 
Sent: Friday, May 24, 2024 2:11 PM
To: Samal, Anil <anil.samal@...el.com>; intel-wired-lan@...ts.osuosl.org
Cc: netdev@...r.kernel.org; Pepiak, Leszek <leszek.pepiak@...el.com>; Kitszel, Przemyslaw <przemyslaw.kitszel@...el.com>; Czapnik, Lukasz <lukasz.czapnik@...el.com>; Nguyen, Anthony L <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