From: Jeff Guo <jia.guo@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: change debug diagnostic message from udev handler
Date: Wed, 19 Aug 2020 11:40:16 +0800 [thread overview]
Message-ID: <22d5df14-26b7-899c-e9b7-ec152d7af9db@intel.com> (raw)
In-Reply-To: <20200814174514.25100-1-stephen@networkplumber.org>
hi, stephen
Agree, it is make sense that the ignore event will sometimes involve the
information which should not be ignore.
On 8/15/2020 1:45 AM, Stephen Hemminger wrote:
> The debug message was poorly worded and did not include the
> part that would be useful. I.e it never said what was being ignored.
> Change it to print the message so that if udev changes format or
> other subsystems need to be added then the necessary information
> will be in the debug log.
>
> Fixes: 0d0f478d0483 ("eal/linux: add uevent parse and process")
> Cc: jia.guo@intel.com
Should this cc line be removed? After that, please and thanks.
Acked-by: Jeff Guo <jia.guo@intel.com>.
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> lib/librte_eal/linux/eal_dev.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/lib/librte_eal/linux/eal_dev.c b/lib/librte_eal/linux/eal_dev.c
> index 83c9cd660754..83b6068264cb 100644
> --- a/lib/librte_eal/linux/eal_dev.c
> +++ b/lib/librte_eal/linux/eal_dev.c
> @@ -234,8 +234,7 @@ dev_uev_handler(__rte_unused void *param)
>
> ret = dev_uev_parse(buf, &uevent, EAL_UEV_MSG_LEN);
> if (ret < 0) {
> - RTE_LOG(DEBUG, EAL, "It is not an valid event "
> - "that need to be handle.\n");
> + RTE_LOG(DEBUG, EAL, "Ignoring uevent '%s'\n", buf);
> return;
> }
>
next prev parent reply other threads:[~2020-08-19 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 17:45 Stephen Hemminger
2020-08-19 3:40 ` Jeff Guo [this message]
2020-09-16 16:20 ` David Marchand
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=22d5df14-26b7-899c-e9b7-ec152d7af9db@intel.com \
--to=jia.guo@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).