From: Doug Ledford <dledford@redhat.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Don Dutile <ddutile@redhat.com>
Cc: Potnuri Bharat Teja <bharat@chelsio.com>,
linux-rdma@vger.kernel.org, nirranjan@chelsio.com
Subject: Re: [PATCH for-next] iw_cxgb3: remove iw_cxgb3 module from kernel.
Date: Fri, 18 Oct 2019 16:51:27 -0400 [thread overview]
Message-ID: <3b6fbc551c3a1c53e9365f6af5889ca38e141d3d.camel@redhat.com> (raw)
In-Reply-To: <20191018204647.GA6087@ziepe.ca>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
On Fri, 2019-10-18 at 17:46 -0300, Jason Gunthorpe wrote:
> On Wed, Oct 16, 2019 at 01:47:29PM -0400, Don Dutile wrote:
>
> > Isn't there a better way to mark a driver deprecated?
> >
> > This kind of removal makes long-term maintenance of such drivers
> > painful in downstream distros, as API changes that are rippled from
> > core through all the drivers, don't update these drivers, and when
> > backporting such API changes to downstream distros, we have to +1
> > removed drivers.
>
> You still have cxg3 as an enabled & supported driver? In RH8? Why?
>
> > It's much easier if upstream continues to update the drivers for
> > such across-the-driver-patch-changes. heck, add a separate patch
> > that punches out a printk stating DEPRECATED (dropping a patch to
> > backport is easy! :) ).
>
> The whole point of doing this is to avoid this work!
People don't quit *using* hardware just because a company has quit
selling it. When we can quit supporting it is more about whether
customers ask for support (or our records indicate lots of systems use
the hardware) than about whether the vendors still care.
That said, we probably could have dropped cxgb3 from 8.0, but I'm not
positive about that. Just a guess.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-18 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 7:42 [PATCH for-next] iw_cxgb3: remove iw_cxgb3 module from kernel Potnuri Bharat Teja
2019-10-04 18:11 ` Jason Gunthorpe
2019-10-17 6:41 ` Adit Ranadive
2019-10-17 8:29 ` Potnuri Bharat Teja
2019-10-18 20:47 ` Jason Gunthorpe
2019-10-18 20:49 ` Doug Ledford
2019-10-10 14:26 ` Michal Kalderon
2019-10-16 17:47 ` Don Dutile
2019-10-17 6:06 ` Leon Romanovsky
2019-10-18 20:46 ` Jason Gunthorpe
2019-10-18 20:51 ` Doug Ledford [this message]
2019-10-18 22:50 ` Don Dutile
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=3b6fbc551c3a1c53e9365f6af5889ca38e141d3d.camel@redhat.com \
--to=dledford@redhat.com \
--cc=bharat@chelsio.com \
--cc=ddutile@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=nirranjan@chelsio.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).