From: Jacob Keller <jacob.e.keller@intel.com>
To: Anil Samal <anil.samal@intel.com>, <intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>, <leszek.pepiak@intel.com>,
<przemyslaw.kitszel@intel.com>, <lukasz.czapnik@intel.com>,
<anthony.l.nguyen@intel.com>
Subject: Re: [PATCH iwl-next v3 0/3] ice:Support to dump PHY config, FEC
Date: Fri, 24 May 2024 14:11:25 -0700 [thread overview]
Message-ID: <2fe273b9-dd6b-408c-bc69-e12c00b4141d@intel.com> (raw)
In-Reply-To: <20240524135255.3607422-1-anil.samal@intel.com>
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
next prev parent reply other threads:[~2024-05-24 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 13:51 [PATCH iwl-next v3 0/3] ice:Support to dump PHY config, FEC Anil Samal
2024-05-24 13:51 ` [PATCH iwl-next v3 1/3] ice: Extend Sideband Queue command to support flags Anil Samal
2024-05-24 20:43 ` [Intel-wired-lan] " Paul Menzel
2024-05-24 21:12 ` Jacob Keller
2024-05-24 13:51 ` [PATCH iwl-next v3 2/3] ice: Implement driver functionality to dump fec statistics Anil Samal
2024-05-24 13:51 ` [PATCH iwl-next v3 3/3] ice: Implement driver functionality to dump serdes equalizer values Anil Samal
2024-06-24 16:28 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2024-05-24 21:11 ` Jacob Keller [this message]
2024-06-08 18:14 ` [PATCH iwl-next v3 0/3] ice:Support to dump PHY config, FEC Samal, Anil
2024-06-10 18:57 ` Jacob Keller
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 12:58 Anil Samal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2fe273b9-dd6b-408c-bc69-e12c00b4141d@intel.com \
--to=jacob.e.keller@intel.com \
--cc=anil.samal@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=leszek.pepiak@intel.com \
--cc=lukasz.czapnik@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).