> -----Original Message-----
> From: Thomas Monjalon <tho...@monjalon.net>
> Sent: Sunday, March 6, 2022 12:56 PM
> To: Wang, Haiyue <haiyue.w...@intel.com>; Zhang, Qi Z
> <qi.z.zh...@intel.com>; ferruh.yi...@intel.com
> Cc: Jeff Daly <je...@silicom-usa.com>; dev@dpdk.org; sta...@dpdk.org;
> Stephen Douthit <steph...@silicom-usa.com>; Lu, Wenzhuo
> <wenzhuo...@intel.com>
> Subject: Re: [PATCH v4 1/3] net/ixgbe: Fix ixgbe_is_sfp() to return valid 
> result for
> X550EM_a devs
> 
> Caution: This is an external email. Please take care when clicking links or
> opening attachments.
> 
> 
> 01/03/2022 12:18, Zhang, Qi Z:
> > From: Wang, Haiyue <haiyue.w...@intel.com>
> > > From: Jeff Daly <je...@silicom-usa.com>
> > > > From: Stephen Douthit <steph...@silicom-usa.com>
> > > >
> > > > Currently all X500EM* MAC types fallthrough to the default case
> > > > and get reported as non-SFP regardless of media type, which isn't 
> > > > correct.
> > > >
> > > > Fixes: 0790adeb567 ("ixgbe/base: support X550em_a device")
> > > > Cc: sta...@dpdk.org
> > > >
> > > > Signed-off-by: Stephen Douthit <steph...@silicom-usa.com>
> > > > Signed-off-by: Jeff Daly <je...@silicom-usa.com>
> > >
> > > Acked-by: Haiyue Wang <haiyue.w...@intel.com>
> >
> > Applied to dpdk-next-net-intel after renaming the title to "fix FSP check 
> > for
> X550EM devices" to fix check-git-log error.
> 
> It seems you have applied only the first patch of the series. Why?
> Is there a good reason to split a series without any justification?
> What about the two other patches?
> 

I should explain the [PATCH v4 x/y] and why it changed from 7 patches to 3 
initially.....     In Stephen's initial v1 of the patch series there were 7 
patches and during the discussion of the v2 version before Stephen left he 
intended to break it into 3 separate submissions.  After speaking with 
Ekinops/Swisscom regarding the best way to move these forward it was decided to 
move some functionality back to ethdev.c.  So currently:  [PATCH v4 1/3] is 
basically [PATCH v2 1/7], [PATCH v2 2/7] and [PATCH v2 5/7] were reworked and 
included in [PATCH v4 3/3] .  [PATCH v2 4/7] became [PATCH v4 2/3].   I 
submitted 2 separate patches yesterday for what was [PATCH v2 6/7] and [PATCH 
v2 7/7] since they were small patches to base/ rather than ethdev.   Finally, 
[PATCH v2 3/7] i'm working out whether it can be reworked into something that 
only touches ethdev (could be more kludgey) or really kinda just fits into base 
as originally submitted, like the last 2 patches I submitted for special 
handling of some SFPs.

I discovered the ixgbe_api functionality the other day while looking into this, 
and was thinking perhaps it could be somehow done there.  Still under base, but 
not touching the main driver files.   Is there any documentation that describes 
the ixgbe_api usage or process to get a wrapper call added to it?

Reply via email to