From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>, Jeff Guo <jia.guo@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eal: change debug diagnostic message from udev handler
Date: Wed, 16 Sep 2020 18:20:19 +0200 [thread overview]
Message-ID: <CAJFAV8w-0fB9UbdL8LzZMRCUmJfAHtqGHLhsmnbv__4aU=_-7w@mail.gmail.com> (raw)
In-Reply-To: <20200814174514.25100-1-stephen@networkplumber.org>
On Fri, Aug 14, 2020 at 7:45 PM Stephen Hemminger
<stephen@networkplumber.org> 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")
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Jeff Guo <jia.guo@intel.com>
Applied.
--
David Marchand
prev parent reply other threads:[~2020-09-16 16:20 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
2020-09-16 16:20 ` David Marchand [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='CAJFAV8w-0fB9UbdL8LzZMRCUmJfAHtqGHLhsmnbv__4aU=_-7w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.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).