From: Ferruh Yigit <ferruh.yigit@intel.com>
To: David Marchand <david.marchand@6wind.com>,
Santosh Shukla <santosh.shukla@caviumnetworks.com>
Cc: dev@dpdk.org, Jerin Jacob <jerin.jacob@caviumnetworks.com>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/octeontx: remove redundent driver name update
Date: Thu, 5 Apr 2018 18:38:49 +0100 [thread overview]
Message-ID: <992b45c2-c804-c514-985f-3cf687cd5a0b@intel.com> (raw)
In-Reply-To: <CALwxeUvZkna3X==rpe-Bxtv_24-bu9mfXjD7qQrSDHagbEc0rQ@mail.gmail.com>
On 4/3/2018 10:06 AM, David Marchand wrote:
> On Mon, Apr 2, 2018 at 6:05 PM, Santosh Shukla
> <santosh.shukla@caviumnetworks.com> wrote:
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
> Reviewed-by: David Marchand <david.marchand@6wind.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-04-05 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 16:05 Santosh Shukla
2018-04-03 9:06 ` David Marchand
2018-04-05 17:38 ` Ferruh Yigit [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=992b45c2-c804-c514-985f-3cf687cd5a0b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=santosh.shukla@caviumnetworks.com \
--cc=stable@dpdk.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).