From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Scott Mitchell <scott.k.mitch1@gmail.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Wathsala Vithanage <wathsala.vithanage@arm.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Jack Bond-Preston <jack.bond-preston@foss.arm.com>,
Jay Wang <jay.wang2@arm.com>, Doug Foster <doug.foster@arm.com>,
Chengwen Feng <fengchengwen@huawei.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH v3 0/5] eal: RTE_PTR_ADD and fix unaligned types
Date: Wed, 23 Sep 2026 21:39:08 +0200 [thread overview]
Message-ID: <9_SWtqM-TYKCyZNk6xgxdQ@monjalon.net> (raw)
In-Reply-To: <20260907183239.629053-1-stephen@networkplumber.org>
This series requires some reviews please,
especially for Arm, mlx5 and EAL parts.
> Scott Mitchell (1):
> eal: RTE_PTR_ADD/SUB API improvements
>
> Stephen Hemminger (4):
> test: fix jhash 32 bit key type
> eal: make unaligned really unaligned
> net/mlx5: drop unnecessary STRICT_ALIGN
> arm: remove no longer used RTE_ARCH_STRICT_ALIGN
next prev parent reply other threads:[~2026-09-23 19:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 22:09 [RFC 0/3] eal: make unaligned types really unaligned Stephen Hemminger
2026-09-04 22:09 ` [RFC 1/3] eal: make unaligned " Stephen Hemminger
2026-09-04 22:09 ` [RFC 2/3] net/mlx5: drop unnecessary STRICT_ALIGN Stephen Hemminger
2026-09-05 10:00 ` Morten Brørup
2026-09-04 22:09 ` [RFC 3/3] arm: remove no longer used RTE_ARCH_STRICT_ALIGN Stephen Hemminger
2026-09-06 17:09 ` [PATCH v2 0/5] eal: RTE_PTR_ADD qualifiers and real unaligned types Stephen Hemminger
2026-09-06 17:09 ` [PATCH v2 1/5] test: fix jhash 32 bit key type Stephen Hemminger
2026-09-06 17:09 ` [PATCH v2 2/5] eal: RTE_PTR_ADD/SUB API improvements Stephen Hemminger
2026-09-06 17:09 ` [PATCH v2 3/5] eal: make unaligned really unaligned Stephen Hemminger
2026-09-06 17:09 ` [PATCH v2 4/5] net/mlx5: drop unnecessary STRICT_ALIGN Stephen Hemminger
2026-09-06 17:09 ` [PATCH v2 5/5] arm: remove no longer used RTE_ARCH_STRICT_ALIGN Stephen Hemminger
2026-09-06 20:14 ` [PATCH v2 0/5] eal: RTE_PTR_ADD qualifiers and real unaligned types Morten Brørup
2026-09-07 18:31 ` [PATCH v3 0/5] eal: RTE_PTR_ADD and fix " Stephen Hemminger
2026-09-07 18:31 ` [PATCH v3 1/5] test: fix jhash 32 bit key type Stephen Hemminger
2026-09-07 18:31 ` [PATCH v3 2/5] eal: RTE_PTR_ADD/SUB API improvements Stephen Hemminger
2026-09-07 18:31 ` [PATCH v3 3/5] eal: make unaligned really unaligned Stephen Hemminger
2026-09-26 16:08 ` Sun Yuechi
2026-09-07 18:31 ` [PATCH v3 4/5] net/mlx5: drop unnecessary STRICT_ALIGN Stephen Hemminger
2026-09-28 9:11 ` Dariusz Sosnowski
2026-09-07 18:31 ` [PATCH v3 5/5] arm: remove no longer used RTE_ARCH_STRICT_ALIGN Stephen Hemminger
2026-09-23 19:39 ` Thomas Monjalon [this message]
2026-10-06 16:15 ` [PATCH v3 0/5] eal: RTE_PTR_ADD and fix unaligned types 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=9_SWtqM-TYKCyZNk6xgxdQ@monjalon.net \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=doug.foster@arm.com \
--cc=dsosnowski@nvidia.com \
--cc=fengchengwen@huawei.com \
--cc=jack.bond-preston@foss.arm.com \
--cc=jay.wang2@arm.com \
--cc=scott.k.mitch1@gmail.com \
--cc=stephen@networkplumber.org \
--cc=viacheslavo@nvidia.com \
--cc=wathsala.vithanage@arm.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