From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH 0/4] more unnecessary function pointer
Date: Tue, 10 Jun 2025 11:39:39 +0200 [thread overview]
Message-ID: <15047382.VsHLxoZxqI@thomas> (raw)
In-Reply-To: <Z9BfD7I1kjvYa_en@bricha3-mobl1.ger.corp.intel.com>
11/03/2025 17:04, Bruce Richardson:
> On Tue, Mar 11, 2025 at 08:51:28AM -0700, Stephen Hemminger wrote:
> > A few more cases where there is unnecessary deref (*) on
> > function pointers.
> >
> > Stephen Hemminger (4):
> > raw/ifpga: remove unnecessary deref of function pointers
> > crypto/ionic: remove unnecessary deref of function pointer
> > regexdev: another unnecessary deref of function pointers
> > vhost: remove unnecessary deref of function pointers
> >
> Series-Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks.
prev parent reply other threads:[~2025-06-10 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 15:51 Stephen Hemminger
2025-03-11 15:51 ` [PATCH 1/4] raw/ifpga: remove unnecessary deref of function pointers Stephen Hemminger
2025-03-11 16:03 ` Bruce Richardson
2025-03-12 14:06 ` Xu, Rosen
2025-03-11 15:51 ` [PATCH 2/4] crypto/ionic: remove unnecessary deref of function pointer Stephen Hemminger
2025-03-19 15:03 ` Boyer, Andrew
2025-03-11 15:51 ` [PATCH 3/4] regexdev: another unnecessary deref of function pointers Stephen Hemminger
2025-03-11 15:51 ` [PATCH 4/4] vhost: remove " Stephen Hemminger
2025-03-11 16:04 ` [PATCH 0/4] more unnecessary function pointer Bruce Richardson
2025-06-10 9:39 ` Thomas Monjalon [this message]
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=15047382.VsHLxoZxqI@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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
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).