netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeed@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Chris Mi <cmi@nvidia.com>,
	netdev@vger.kernel.org, jiri@nvidia.com,
	kernel test robot <lkp@intel.com>,
	Ido Schimmel <idosch@idosch.org>
Subject: Re: [PATCH net-next v6] net: psample: Introduce stubs to remove NIC driver dependency
Date: Tue, 02 Feb 2021 13:43:17 -0800	[thread overview]
Message-ID: <033388a2b5cd97d879c5dea20c24c1f7a825d812.camel@kernel.org> (raw)
In-Reply-To: <20210202132446.11d3af03@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Tue, 2021-02-02 at 13:24 -0800, Jakub Kicinski wrote:
> On Mon, 01 Feb 2021 23:31:15 -0800 Saeed Mahameed wrote:

...

> > 
> > Jakub, it is not only about installation dependencies, the issue is
> > more critical than this, 
> > 
> > We had some other issues with similar dependency problem where
> > mlx5_core had hard dependency with netfilter, firewalld when
> > disabled,
> > removes netfilter and all its dependencies including mlx5, this is
> > a no
> > go for our users.
> > 
> > Again, having a hard dependency between a hardware driver and a
> > peripheral module in the kernel is a bad design.
> 
> That is not the point.
> 
> The technical problem is minor, and it's a problem for _your_ driver.
> Yet, it appears to be my responsibility to make sure the patch even
> compiles.
> 

I understand your frustration, We should have been more professional
with this patch submission, 

> I believe there should be a limit to the ignorance a community
> volunteer is expected to put up with when dealing with patches 
> from and for the benefit of a commercial vendor.
> 

totally agree, we have the tools internally to avoid clutter in mailing
list and we do this for pure mlx5 patches, but for net patches, people
tend to hurry and skip the queue so they get feedback ASAP.. 
this doesn't make it right, I will work to improve this.

> This is up for discussion, if you disagree let's talk it out. I'm 
> not particularly patient (to put it mildly), but I don't understand 
> how v5 could have built, and yet v6 gets posted with the same exact
> problem :/
> 

given the circumstance i would've done the same, even on v4.. 
sorry for the inconvenience .. :(.. thanks for your patience. 

> So from my perspective it seems like the right step to push back.

And I back you up !

> If you, Tariq, Jiri, Ido or any other seasoned kernel contributor
> reposts this after making sure it's up to snuff themselves I will
> most certainly take a look / apply.

My point wasn't about psample, it's about hw drivers vs stack/modules
dependency in general, maybe I used the wrong patch to discuss this
matter :D.. 

I will post a separate RFC for discussion later not related to psample
at all. this patch smells so bad we can't even discuss the general
issue here ..

Again thanks for your review and patience.




  reply	other threads:[~2021-02-02 21:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01  2:04 [PATCH net-next v6] net: psample: Introduce stubs to remove NIC driver dependency Chris Mi
2021-02-02  1:14 ` Jakub Kicinski
2021-02-02  7:31   ` Saeed Mahameed
2021-02-02 21:24     ` Jakub Kicinski
2021-02-02 21:43       ` Saeed Mahameed [this message]
2021-02-03  2:55       ` Chris Mi

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=033388a2b5cd97d879c5dea20c24c1f7a825d812.camel@kernel.org \
    --to=saeed@kernel.org \
    --cc=cmi@nvidia.com \
    --cc=idosch@idosch.org \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.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 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).