From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Gur Stavi <gur.stavi@huawei.com>
Cc: dev@dpdk.org, "John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH v02] net/af_packet: support link status update
Date: Thu, 17 Oct 2024 00:29:49 +0100 [thread overview]
Message-ID: <b0ca4c76-17cd-4df7-99ac-239cc3692e72@amd.com> (raw)
In-Reply-To: <20241015081951.24ac3608@hermes.local>
On 10/15/2024 4:19 PM, Stephen Hemminger wrote:
> On Tue, 15 Oct 2024 12:57:29 +0300
> Gur Stavi <gur.stavi@huawei.com> wrote:
>
>> For net_af_packet PMD, eth_link_update was an empty function.
>> Application may be interested in link up/down status.
>> This patch adds implementation that updates dev_link->link_status based
>> on socket IFF_RUNNING flag.
>>
>> Signed-off-by: Gur Stavi <gur.stavi@huawei.com>
>> ---
>> v2:
>> * return error on ioctl error
>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-10-16 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 9:57 Gur Stavi
2024-10-15 15:19 ` Stephen Hemminger
2024-10-16 23:29 ` Ferruh Yigit [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=b0ca4c76-17cd-4df7-99ac-239cc3692e72@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=gur.stavi@huawei.com \
--cc=linville@tuxdriver.com \
--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).