Re: compilation|FAILURE| pw(149211) sid(34143) job(PER_PATCH_BUILD14361)[v2, 3/3] eal: enhance lock annotations for rwlock

2024-12-30 Thread Liao, TingtingX
Sorry. There is no error with this series. The error is caused by the CI doesn't apply any changes with doc/*. Community decided to exclude doc/*, as doc/* change frequently, especially the release notes, cause a lot of conflict with main tree. Thanks, Tingting

Recall: Re: compilation|FAILURE| pw(149211) sid(34143) job(PER_PATCH_BUILD14361)[v2, 3/3] eal: enhance lock annotations for rwlock

2024-12-30 Thread Liao, TingtingX
tingtingx.l...@intel.com would like to recall the message, "Re: compilation|FAILURE| pw(149211) sid(34143) job(PER_PATCH_BUILD14361)[v2, 3/3] eal: enhance lock annotations for rwlock".

[PATCH v4 3/3] drivers/net: add diagnostics macros to make code portable

2024-12-30 Thread Andre Muezerie
It was a common pattern to have "GCC diagnostic ignored" pragmas sprinkled over the code and only activate these pragmas for certain compilers (gcc and clang). Clang supports GCC's pragma for compatibility with existing source code, so #pragma GCC diagnostic and #pragma clang diagnostic are synonym

[PATCH v4 0/3] add diagnostics macros to make code portable

2024-12-30 Thread Andre Muezerie
It was a common pattern to have "GCC diagnostic ignored" pragmas sprinkled over the code and only activate these pragmas for certain compilers (gcc and clang). Clang supports GCC's pragma for compatibility with existing source code, so #pragma GCC diagnostic and #pragma clang diagnostic are synonym

[PATCH v4 1/3] lib/eal: add diagnostics macros to make code portable

2024-12-30 Thread Andre Muezerie
It was a common pattern to have "GCC diagnostic ignored" pragmas sprinkled over the code and only activate these pragmas for certain compilers (gcc and clang). Clang supports GCC's pragma for compatibility with existing source code, so #pragma GCC diagnostic and #pragma clang diagnostic are synonym

[PATCH v4 2/3] drivers/common: add diagnostics macros to make code portable

2024-12-30 Thread Andre Muezerie
It was a common pattern to have "GCC diagnostic ignored" pragmas sprinkled over the code and only activate these pragmas for certain compilers (gcc and clang). Clang supports GCC's pragma for compatibility with existing source code, so #pragma GCC diagnostic and #pragma clang diagnostic are synonym

Re: compilation|FAILURE| pw(149211) sid(34143) job(PER_PATCH_BUILD14361)[v2, 3/3] eal: enhance lock annotations for rwlock

2024-12-30 Thread Liao, TingtingX
Sorry. There is no error with this series. The error is caused by the CI doesn't apply any changes with doc/*. Community decided to exclude doc/*, as doc/* change frequently, especially the release notes, cause a lot of conflict with main tree. Thanks, Tingting

Re: [PATCH v4 0/3] add diagnostics macros to make code portable

2024-12-30 Thread Stephen Hemminger
On Mon, 30 Dec 2024 07:59:27 -0800 Andre Muezerie wrote: > From: Andre Muezerie > To: andre...@linux.microsoft.com > Cc: dev@dpdk.org, step...@networkplumber.org > Subject: [PATCH v4 0/3] add diagnostics macros to make code portable > Date: Mon, 30 Dec 2024 07:59:27 -0800 > X-Mailer: git-send-e

Re: [PATCH 1/3] net/hns3: fix simple Tx path incorrect free the mbuf

2024-12-30 Thread Stephen Hemminger
On Mon, 30 Dec 2024 14:54:03 +0800 Jie Hai wrote: > From: Jie Hai > To: , , , > , , Chengwen Feng > , "Wei Hu (Xavier)" , > Huisong Li > CC: , > Subject: [PATCH 1/3] net/hns3: fix simple Tx path incorrect free the mbuf > Date: Mon, 30 Dec 2024 14:54:03 +0800 > X-Mailer: git-send-email 2.

Re: [PATCH 0/3] net/hns3: bugfix on hns3

2024-12-30 Thread Stephen Hemminger
On Mon, 30 Dec 2024 14:54:02 +0800 Jie Hai wrote: > From: Jie Hai > To: , , , > , > CC: , , , > > Subject: [PATCH 0/3] net/hns3: bugfix on hns3 > Date: Mon, 30 Dec 2024 14:54:02 +0800 > X-Mailer: git-send-email 2.22.0 > > The patchset fixes some codes. > > Dengdui Huang (1): > net/hns3

[PATCH] service: add service maintenance callback

2024-12-30 Thread Piotr Krzewinski
Add option to register a callback running on service lcores along regular services, which gets information about the service loop. It enables doing maintenance work or power saving during periods when all registered services are idling. As an example application that is doing dequeue from multiple