From: Yongseok Koh <yskoh@mellanox.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Matan Azrad <matan@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx: prefix private structure
Date: Thu, 21 Feb 2019 13:01:44 +0000 [thread overview]
Message-ID: <8689A300-A2B9-4B31-B4B4-1945AEF423CB@mellanox.com> (raw)
In-Reply-To: <20190221092914.4822-1-thomas@monjalon.net>
> On Feb 21, 2019, at 1:29 AM, Thomas Monjalon <thomas@monjalon.net> wrote:
>
> The private structure stored in rte_eth_dev->data->dev_private
> was named "struct priv".
> In order to ease code browsing, the structure is renamed
> "struct mlx[45]_priv".
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
Please add "Cc: stable@dpdk.org" when merging it.
We can minimize conflict and manual labor,
when automatically applying bug fixes to stable releases.
Acked-by: Yongseok Koh <yskoh@mellanox.com>
Thanks
next prev parent reply other threads:[~2019-02-21 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 9:29 Thomas Monjalon
2019-02-21 13:01 ` Yongseok Koh [this message]
2019-02-24 6:56 ` Shahaf Shuler
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=8689A300-A2B9-4B31-B4B4-1945AEF423CB@mellanox.com \
--to=yskoh@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=shahafs@mellanox.com \
--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).