DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kinsella, Ray" <mdr@ashroe.eu>
To: Thomas Monjalon <thomas@monjalon.net>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>,
	Jerin Jacob <jerinj@marvell.com>
Cc: Jerin Jacob <jerinjacobk@gmail.com>,
	dev@dpdk.org, Harman Kalra <hkalra@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH 1/7] common/octeontx: enable build only on 64bit Linux
Date: Thu, 25 Mar 2021 10:58:15 +0000	[thread overview]
Message-ID: <5cb9bec3-6d4e-7867-e8d7-9c3d55ec78ef@ashroe.eu> (raw)
In-Reply-To: <11975004.s7UMkAiPBC@thomas>



On 25/03/2021 10:46, Thomas Monjalon wrote:
> 25/03/2021 11:42, Thomas Monjalon:
>> 24/03/2021 11:55, Jerin Jacob:
>>> On Thu, Feb 25, 2021 at 10:33 PM <pbhagavatula@marvell.com> wrote:
>>>>
>>>> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>>>>
>>>> Due to Linux kernel dependency, only enable build for 64bit Linux.
>>>>
>>>> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
>>>
>>> Series Acked-by: Jerin Jacob <jerinj@marvell.com>
>>
>> I've reorganized the commits per family of drivers,
>> so it makes more sense than grouping per driver class
>> with "common/octeontx" for title for all:
>>
>> net/thunderx: enable build only on 64-bit Linux
>> common/octeontx: enable build only on 64-bit Linux
>> common/octeontx2: enable build only on 64-bit Linux
>>
>> and applied.
> 
> Actually not applied yet.
> I'm not sure what to do for the ABI check which is broken
> because some drivers are not compiled anymore in 32-bit build.
> I've workarounded locally by removing the dump files in the reference build.
> Should we add an exception in libabigail.abignore?
> 
In the past we said that depreciating HW support would be considered to be same as an ABI Breakage.

From the policy ... 
"Updates to the minimum hardware requirements, which drop support for hardware which was previously supported, should be treated as an ABI change."


  reply	other threads:[~2021-03-25 10:58 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 17:02 pbhagavatula
2021-02-25 17:02 ` [dpdk-dev] [PATCH 2/7] mempool/octeontx: " pbhagavatula
2021-02-25 17:02 ` [dpdk-dev] [PATCH 3/7] net/octeontx: " pbhagavatula
2021-02-25 17:02 ` [dpdk-dev] [PATCH 4/7] crypto/octeontx: " pbhagavatula
2021-02-25 17:02 ` [dpdk-dev] [PATCH 5/7] event/octeontx: " pbhagavatula
2021-02-25 17:02 ` [dpdk-dev] [PATCH 6/7] raw/octeontx2: enable build only for " pbhagavatula
2021-03-22 15:14   ` Radha Mohan
2021-02-25 17:02 ` [dpdk-dev] [PATCH 7/7] compress/octeontx: " pbhagavatula
2021-02-26  5:52   ` Ashish Gupta
2021-03-24 10:55 ` [dpdk-dev] [PATCH 1/7] common/octeontx: enable build only on " Jerin Jacob
2021-03-25 10:42   ` Thomas Monjalon
2021-03-25 10:46     ` Thomas Monjalon
2021-03-25 10:58       ` Kinsella, Ray [this message]
2021-03-25 11:03         ` Thomas Monjalon
2021-03-25 12:46           ` Jerin Jacob
2021-03-25 12:47             ` Kinsella, Ray
2021-03-25 12:58               ` Jerin Jacob
2021-03-25 13:02                 ` Kinsella, Ray
2021-03-26 10:50                   ` Jerin Jacob
2021-03-25 14:57             ` Thomas Monjalon
2021-03-25 15:01               ` David Marchand
2021-03-25 14:52 ` [dpdk-dev] [PATCH 21.11 v2 0/3] octeontx build only on 64-bit Linux Thomas Monjalon
2021-03-25 14:52   ` [dpdk-dev] [PATCH 21.11 v2 1/3] net/thunderx: enable " Thomas Monjalon
2021-08-23 19:54     ` [dpdk-dev] [PATCH v3 " pbhagavatula
2021-08-23 19:54       ` [dpdk-dev] [PATCH v3 2/3] common/octeontx: " pbhagavatula
2021-08-23 19:54       ` [dpdk-dev] [PATCH v3 3/3] common/octeontx2: " pbhagavatula
2021-09-07 12:14       ` [dpdk-dev] [PATCH v3 1/3] net/thunderx: " Ferruh Yigit
2021-10-03 20:36       ` [dpdk-dev] [PATCH v4 " pbhagavatula
2021-10-03 20:36         ` [dpdk-dev] [PATCH v4 2/3] common/octeontx: " pbhagavatula
2021-10-03 20:36         ` [dpdk-dev] [PATCH v4 3/3] common/octeontx2: " pbhagavatula
2021-10-04  5:56         ` [dpdk-dev] [PATCH v5 1/3] net/thunderx: " pbhagavatula
2021-10-04  5:56           ` [dpdk-dev] [PATCH v5 2/3] common/octeontx: " pbhagavatula
2021-10-04  5:56           ` [dpdk-dev] [PATCH v5 3/3] common/octeontx2: " pbhagavatula
2021-10-04  9:05           ` [dpdk-dev] [PATCH v5 1/3] net/thunderx: " Ferruh Yigit
2021-10-14 19:56           ` [dpdk-dev] [PATCH v6 " pbhagavatula
2021-10-14 19:56             ` [dpdk-dev] [PATCH v6 2/3] common/octeontx: " pbhagavatula
2021-10-18  7:03               ` Harman Kalra
2021-10-14 19:56             ` [dpdk-dev] [PATCH v6 3/3] common/octeontx2: " pbhagavatula
2021-10-15 10:39             ` [dpdk-dev] [PATCH v6 1/3] net/thunderx: " Ferruh Yigit
2021-10-15 13:58               ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2021-10-15 16:32                 ` Ferruh Yigit
2021-10-15 17:16             ` [dpdk-dev] " Ferruh Yigit
2021-03-25 14:52   ` [dpdk-dev] [PATCH 21.11 v2 2/3] common/octeontx: " Thomas Monjalon
2021-03-25 14:52   ` [dpdk-dev] [PATCH 21.11 v2 3/3] common/octeontx2: " Thomas Monjalon
2021-08-17  8:46   ` [dpdk-dev] [PATCH 21.11 v2 0/3] octeontx " David Marchand

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=5cb9bec3-6d4e-7867-e8d7-9c3d55ec78ef@ashroe.eu \
    --to=mdr@ashroe.eu \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=ndabilpuram@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=thomas@monjalon.net \
    /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).