patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [PATCH v11 0/3] Fix cmdline_poll and testpmd signal handling
Date: Tue, 7 Feb 2023 14:48:52 +0000	[thread overview]
Message-ID: <88a9871e-c202-b778-f2cc-2e755a3b3770@amd.com> (raw)
In-Reply-To: <20230203191409.97567-1-stephen@networkplumber.org>

On 2/3/2023 7:14 PM, Stephen Hemminger wrote:
> This patchset keeps uncovering bad practices in the cmdline library
> around end of file and signal handling.
> 
> Stephen Hemminger (3):
>   cmdline: make rdline status not private
>   cmdline: handle EOF in cmdline_poll
>   testpmd: cleanup cleanly from signal

Tested-by: Ferruh Yigit <ferruh.yigit@amd.com>

  parent reply	other threads:[~2023-02-07 14:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230130200914.22049-1-stephen@networkplumber.org>
2023-02-03 19:14 ` Stephen Hemminger
2023-02-03 19:14   ` [PATCH v11 1/3] cmdline: make rdline status not private Stephen Hemminger
2023-02-06  2:31     ` fengchengwen
2023-02-03 19:14   ` [PATCH v11 2/3] cmdline: handle EOF in cmdline_poll Stephen Hemminger
2023-02-03 19:14   ` [PATCH v11 3/3] testpmd: cleanup cleanly from signal Stephen Hemminger
2023-02-07 14:49     ` Ferruh Yigit
2023-02-07 14:48   ` Ferruh Yigit [this message]
2023-02-19 17:53   ` [PATCH v11 0/3] Fix cmdline_poll and testpmd signal handling Stephen Hemminger
2023-03-11 10:17     ` Thomas Monjalon
2023-03-12 17:18       ` Tal Shnaiderman
2023-03-13 10:34         ` Ling, WeiX
2023-03-13 15:53           ` Stephen Hemminger
2023-03-14  7:05             ` Ling, WeiX

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=88a9871e-c202-b778-f2cc-2e755a3b3770@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=stable@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).