All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2 1/1] ixgbe: correct SDP0 check of SFP cage for X550
Date: Tue, 10 May 2022 13:28:47 +0200	[thread overview]
Message-ID: <YnpMbwAFMnYTrc33@boxer> (raw)
In-Reply-To: <BL0PR11MB299331AAD0B587D12B965D5899C99@BL0PR11MB2993.namprd11.prod.outlook.com>

On Tue, May 10, 2022 at 11:21:42AM +0000, Skajewski, PiotrX wrote:
> Hi Jeff,
> 
> Our analysis (using 0x15c4) showed that every time the cage is empty SDP indicates 0 and when cage is full it indicates 1.
> No matter what transceiver we used, from those we have.

Please wrap your sentences to 75 chars per line, people that read mailing
lists will be grateful for that.

> The same happens even we don't use the device which fall into crosstalk fix e.g 0x15c2.
> 
> When proposed patch was applied, the devices are no longer able to negotiate speed.
> so basically this patch should not be accepted.

We don't know what you're referring to. Please respond to the patch
itself rather than carrying only the subject of the patch.

> 
> NACK
> 
> BR,
> Piotr
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2022-05-10 11:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 11:21 [Intel-wired-lan] [PATCH v2 1/1] ixgbe: correct SDP0 check of SFP cage for X550 Skajewski, PiotrX
2022-05-10 11:28 ` Maciej Fijalkowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-20 20:51 [Intel-wired-lan] [PATCH " Jeff Daly
2022-04-25 13:17 ` [Intel-wired-lan] [PATCH v2 " Jeff Daly
2022-05-11  8:32   ` Piotr Skajewski
2022-05-12 17:09   ` Tony Nguyen
2022-05-13 20:38     ` Jeff Daly

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=YnpMbwAFMnYTrc33@boxer \
    --to=maciej.fijalkowski@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.