From: Kevin Traynor <ktraynor@redhat.com> To: Ajit Khaparde <ajit.khaparde@broadcom.com> Cc: dpdk-dev <dev@dpdk.org> Subject: Re: [dpdk-dev] [PATCH] doc: announce end of support for some Broadcom devices Date: Fri, 6 Nov 2020 19:22:09 +0000 Message-ID: <29946ac0-7b75-e66e-49ab-c2166507ea95@redhat.com> (raw) In-Reply-To: <CACZ4nhtnKH5pxScico2DgMyd4X8UZ7mf-JZReTxApL1E+abxHQ@mail.gmail.com> On 03/11/2020 17:26, Ajit Khaparde wrote: > On Tue, Nov 3, 2020 at 2:50 AM Kevin Traynor <ktraynor@redhat.com> wrote: >> >> Hi Ajit, >> >> On 26/10/2020 21:46, Ajit Khaparde wrote: >>> Devices belonging to BCM573xx and BCM5740x family will not be supported >>> from the 21.02 release. >>> >>> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> >>> --- >>> doc/guides/rel_notes/deprecation.rst | 6 ++++++ >>> 1 file changed, 6 insertions(+) >>> >>> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst >>> index 2e082499b8..f1fce4210d 100644 >>> --- a/doc/guides/rel_notes/deprecation.rst >>> +++ b/doc/guides/rel_notes/deprecation.rst >>> @@ -166,3 +166,9 @@ Deprecation Notices >>> ``make``. Given environments are too much variables for such a simple script, >>> it will be removed in DPDK 20.11. >>> Some useful parts may be converted into specific scripts. >>> + >>> +* Broadcom bnxt PMD: NetXtreme devices belonging to the ``BCM573xx and >>> + BCM5740x`` families will no longer be supported as of DPDK 21.02. >>> + Specifically the support for the following Broadcom PCI ids will be removed >>> + from the release: ``0x16c8, 0x16c9, 0x16ca, 0x16ce, 0x16cf, 0x16df,`` >>> + ``0x16d0, 0x16d1, 0x16d2, 0x16d4, 0x16d5, 0x16e7, 0x16e8, 0x16e9``. >>> >> >> It might be worth adding to the bnxt.rst section about these NICs, as >> there is no hint that they are deprecated for a user reading that. > Thanks Kevin. > I will add that when the support is really removed. > > Since the deprecation is not really planned for 20.11 I think it is not really > needed for now? > Ok, it's the correct section for it, so I won't argue. >> >> Where I'm not clear is about 20.11. It will be an LTS, will they be >> supported for the lifetime of 20.11 on the 20.11 branch? > 20.11 will have the support. The deprecation is planned for 21.02. > Right, I'm just concerned about it getting broken in say 20.11.2 because of backports to the driver. Once it's in 20.11, it should continue to work in 20.11.x releases which will be for 2 years. Anyway, that is a side issue to this patch for deprecation, so, Acked-by: Kevin Traynor <ktraynor@redhat.com> > Thanks > Ajit > >> >> Kevin. >>
next prev parent reply other threads:[~2020-11-06 19:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-26 21:46 Ajit Khaparde 2020-11-03 10:50 ` Kevin Traynor 2020-11-03 17:26 ` Ajit Khaparde 2020-11-06 19:22 ` Kevin Traynor [this message] 2020-11-06 20:59 ` Ajit Khaparde 2020-11-20 17:30 ` Ajit Khaparde 2020-11-22 20:15 ` Thomas Monjalon 2020-11-23 14:56 ` Ajit Khaparde 2020-11-24 15:34 ` Ferruh Yigit 2020-11-25 8:48 ` Jerin Jacob 2020-11-26 11:31 ` Bruce Richardson 2020-11-26 16:52 ` Thomas Monjalon
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=29946ac0-7b75-e66e-49ab-c2166507ea95@redhat.com \ --to=ktraynor@redhat.com \ --cc=ajit.khaparde@broadcom.com \ --cc=dev@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
DPDK patches and discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \ dev@dpdk.org public-inbox-index dev Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git