From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Martin Spinler <spinler@cesnet.cz>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>, <dev@dpdk.org>
Subject: Re: [PATCH v2] net/szedata2: remove driver
Date: Thu, 11 Nov 2021 09:26:59 +0000 [thread overview]
Message-ID: <9d54ca22-b4ae-ca90-e02d-0cce578b4c14@intel.com> (raw)
In-Reply-To: <c9cc17a0c25f2f024205ccaf54fe4d8941fcbe6a.camel@cesnet.cz>
On 11/11/2021 9:08 AM, Martin Spinler wrote:
> On Wed, 2021-11-10 at 16:08 +0000, Ferruh Yigit wrote:
>> On 11/10/2021 3:39 PM, Martin Spinler wrote:
>>> Remove the szedata2 device driver as the platform is no longer
>>> supported.
>>>
>>> Signed-off-by: Martin Spinler<spinler@cesnet.cz>
>>
>> Thanks Martin for the update.
>>
>> It would be better to announce the removal a release in advance,
>> to let possible users know about it and cover themselves.
>> This is what our device deprecation policy.
>
> I'm sorry for that, I've missed that point.
>
>>
>> But for this case, keeping the driver in this release will mean
>> to maintain it in the LTS for two more years. Because of this I am
>> OK to remove the driver, but cc'ed techboard for any objection.
>>
>>
>> Also I don't know if device was available in the public market,
>> what is the chance to have the users using this device without
>> your company's knowledge.
>
> The devices were sold and supported directly by the Netcope
> Technologies. I asked them about driver removal and they think it will
> not affect any customer.
>
This is what I was expecting, so the impact of removal is minimum.
next prev parent reply other threads:[~2021-11-11 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 15:39 Martin Spinler
2021-11-10 16:08 ` Ferruh Yigit
2021-11-11 9:08 ` Martin Spinler
2021-11-11 9:26 ` Ferruh Yigit [this message]
2021-11-15 15:52 ` Ferruh Yigit
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=9d54ca22-b4ae-ca90-e02d-0cce578b4c14@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=spinler@cesnet.cz \
--cc=techboard@dpdk.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).