Re: [PATCH] Move rmnet out of NET_VENDOR_QUALCOMM dependency

[Justin Forbes]

On Fri, Jul 7, 2023 at 4:12 PM Jakub Kicinski <kuba@xxxxxxxxxx> wrote:
>
> On Fri, 7 Jul 2023 11:50:16 -0500 Justin Forbes wrote:
> > > On Thu,  6 Jul 2023 09:51:52 -0500 Justin M. Forbes wrote:
> > > > The rmnet driver is useful for chipsets that are not hidden behind
> > > > NET_VENDOR_QUALCOMM.  Move sourcing the rmnet Kconfig outside of the if
> > > > NET_VENDOR_QUALCOMM as there is no dependency here.
> > > >
> > > > Signed-off-by: Justin M. Forbes <jforbes@xxxxxxxxxxxxxxxxx>
> > >
> > > Examples of the chipsets you're talking about would be great to have in
> > > the commit message.
> >
> > The user in the Fedora bug was using mhi_net with qmi_wwan.
>
> Hm, if anything mhi_net should not be sitting directly in drivers/net/
>
> I don't think this is a change in the right direction, just enable
> VENDOR_QUALCOMM? Or am I missing something?

Enabling it is not a problem, but it seems that if devices not hidden
behind VENDOR_QUALCOMM are able to use rmnet, then it is incorrect for
rmnet to be hidden behind VENDOR_QUALCOMM. I have already enabled
everything for Fedora users, so I am not worried about how to support
my users, just a matter of correctness, and the fact that Kconfig deps
are more difficult for people to understand in general.   Someone
reading online hears they need to turn on rmnet, so they add an entry
for it, and don't realize that the entry is ignored because
VENDOR_QUALCOMM is not enabled.  Either all devices capable of using
rmnet should be hidden behind VENDOR_QUALCOMM or rmnet should not be.

Justin