From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Dekel Peled <dekelp@mellanox.com>, <ferruh.yigit@intel.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: Mon, 1 Apr 2019 11:52:13 +0300 [thread overview]
Message-ID: <469b7cf9-a617-01f7-4eb4-9c9e92b71409@solarflare.com> (raw)
Message-ID: <20190401085213.WrVd_YGLwEMw0lReuPqwjMtdQMWdzGzIyyaG8QNJufQ@z> (raw)
In-Reply-To: <1554029208-26724-1-git-send-email-dekelp@mellanox.com>
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>
next prev parent reply other threads:[~2019-04-01 8:52 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 [this message]
2019-04-01 8:52 ` Andrew Rybchenko
2019-04-02 15:34 ` Ferruh Yigit
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=469b7cf9-a617-01f7-4eb4-9c9e92b71409@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).