From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Hunt, David" <david.hunt@intel.com>
Subject: Re: [PATCH] sw_evdev: report correct device name
Date: Tue, 13 Sep 2022 19:41:52 +0530 [thread overview]
Message-ID: <CALBAE1OBU+wFixCcf8GS2hJuiaOfuXLRgydi5OQuNCyxBmz+ag@mail.gmail.com> (raw)
In-Reply-To: <BN0PR11MB571258BA5C744C5E5182FF95D7889@BN0PR11MB5712.namprd11.prod.outlook.com>
On Thu, Jul 14, 2022 at 1:15 PM Van Haaren, Harry
<harry.van.haaren@intel.com> wrote:
>
> > -----Original Message-----
> > From: Stephen Hemminger <stephen@networkplumber.org>
> > Sent: Wednesday, July 13, 2022 7:25 PM
> > To: dev@dpdk.org
> > Cc: Stephen Hemminger <stephen@networkplumber.org>; Van Haaren, Harry
> > <harry.van.haaren@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>;
> > Hunt, David <david.hunt@intel.com>
> > Subject: [PATCH] sw_evdev: report correct device name
> >
> > The software eventdev PMD reports todo-fix-name as the
> > device name. Looks like simple fix.
> >
> > Fixes: c66baa68e453 ("event/sw: add dump function for easier debugging")
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> Simple fix, but does what it needs! Thanks;
>
> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
Updated the git commit as follows to fix ./devtools/check-git-log.sh
issues and applied to dpdk-next-net-eventdev/for-main. Thanks
event/sw: report correct device name
The software eventdev PMD reports todo-fix-name as the
device name.
Fixes: c66baa68e453 ("event/sw: add dump function for easier debugging")
Cc: stable@dpdk.org
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
>
> <snip diff>
prev parent reply other threads:[~2022-09-13 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 18:24 Stephen Hemminger
2022-07-14 7:45 ` Van Haaren, Harry
2022-09-13 14:11 ` Jerin Jacob [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=CALBAE1OBU+wFixCcf8GS2hJuiaOfuXLRgydi5OQuNCyxBmz+ag@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@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).