From: Stephen Hemminger <stephen@networkplumber.org>
To: fengchengwen <fengchengwen@huawei.com>
Cc: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>,
<stable@dpdk.org>, Chas Williams <chas3@att.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Declan Doherty <declan.doherty@intel.com>
Subject: Re: [PATCH] net/bonding: fix link status callback stop
Date: Mon, 16 Oct 2023 08:54:41 -0700 [thread overview]
Message-ID: <20231016085441.4b3544b0@hermes.local> (raw)
In-Reply-To: <8e752c64-1e94-7147-6f65-e9e924e998ab@huawei.com>
On Mon, 16 Oct 2023 18:33:01 +0800
fengchengwen <fengchengwen@huawei.com> wrote:
> > + if (internals->link_status_polling_enabled) {
> > + rte_eal_alarm_cancel(bond_ethdev_member_link_status_change_monitor,
> > + (void *)&rte_eth_devices[internals->port_id]);
Is the cast to void * actually necessary?
prev parent reply other threads:[~2023-10-16 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 8:47 David Marchand
2023-10-16 10:33 ` fengchengwen
2023-10-16 12:22 ` Ferruh Yigit
2023-10-16 15:54 ` Stephen Hemminger [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=20231016085441.4b3544b0@hermes.local \
--to=stephen@networkplumber.org \
--cc=chas3@att.com \
--cc=david.marchand@redhat.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=humin29@huawei.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@dpdk.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).