From: "Morten Brørup" <mb@smartsharesystems.com>
To: "David Marchand" <david.marchand@redhat.com>, <jerinj@marvell.com>
Cc: <dev@dpdk.org>, "Thomas Monjalon" <thomas@monjalon.net>
Subject: RE: [PATCH v7 1/4] net/bnx2x: fix warnings about rte_memcpy lengths
Date: Thu, 09 Mar 2023 11:29:27 +0100 [thread overview]
Message-ID: <003a01d95272$06bc4392$0a04a8c0@smartsharesys.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
Please wait. Jerin is chasing this internally.-MortenSent from smartphone. Please excuse brevity and spelling.
-------- Oprindelig besked --------Fra: David Marchand <david.marchand@redhat.com> Dato: 09.03.2023 11.26 (GMT+01:00) Til: Morten Brørup <mb@smartsharesystems.com>, rmody@marvell.com, shshaikh@marvell.com Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net> Emne: Re: [PATCH v7 1/4] net/bnx2x: fix warnings about rte_memcpy lengths On Thu, Feb 9, 2023 at 5:49 PM Morten Brørup <mb@smartsharesystems.com> wrote:>> PING bnx2x maintainers. Care to review this bugfix, so it can be included in 23.03?>Still no luck in getting attention from bnx2x maintainers.One option is to declare this driver as UNMAINTAINED and disable itscompilation when the memcpy annotations are finalised and merged in anext release.-- David Marchand
[-- Attachment #2: Type: text/html, Size: 1512 bytes --]
next reply other threads:[~2023-03-09 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 10:29 Morten Brørup [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-02 15:34 [PATCH] eal: add nonnull and access function attributes Morten Brørup
2023-01-16 13:07 ` [PATCH v7 1/4] net/bnx2x: fix warnings about rte_memcpy lengths Morten Brørup
2023-02-09 16:49 ` Morten Brørup
2023-03-09 10:25 ` David Marchand
2023-03-09 10:33 ` Thomas Monjalon
2023-03-09 16:11 ` [EXT] " Akhil Goyal
[not found] ` <SJ0PR18MB390039A8C34E485F8D2D518EA1B59@SJ0PR18MB3900.namprd18.prod.outlook.com>
2023-03-09 16:19 ` Devendra Singh Rawat
2023-03-09 16:23 ` Stephen Hemminger
2024-02-23 12:39 ` Jerin Jacob
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='003a01d95272$06bc4392$0a04a8c0@smartsharesys.local' \
--to=mb@smartsharesystems.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@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).