From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
Dekel Peled <dekelp@mellanox.com>,
thomas@monjalon.net
Cc: dev@dpdk.org, orika@mellanox.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] rte_ethdev: fix typos in error log message
Date: Tue, 2 Apr 2019 16:34:04 +0100 [thread overview]
Message-ID: <9bb48147-e052-8fc8-ff9f-1586d341c7a6@intel.com> (raw)
In-Reply-To: <469b7cf9-a617-01f7-4eb4-9c9e92b71409@solarflare.com>
On 4/1/2019 9:52 AM, Andrew Rybchenko wrote:
> On 3/31/19 1:46 PM, Dekel Peled wrote:
>> Correct minor typing mistake:
>> pre-queue ==> per-queue
>>
>> Fixes: bea1e0c70cfc ("ethdev: convert static log type usage to dynamic")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
>
>
> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>
>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-04-02 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 10:46 Dekel Peled
2019-03-31 10:46 ` Dekel Peled
2019-04-01 8:52 ` Andrew Rybchenko
2019-04-01 8:52 ` Andrew Rybchenko
2019-04-02 15:34 ` Ferruh Yigit [this message]
2019-04-02 15:34 ` Ferruh Yigit
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=9bb48147-e052-8fc8-ff9f-1586d341c7a6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).