From: sshukla <sshukla@caviumnetworks.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Santosh Shukla <santosh.shukla@caviumnetworks.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com,
jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com,
anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH v3 0/6] make dpdk iova aware
Date: Mon, 23 Oct 2017 20:46:09 +0530 [thread overview]
Message-ID: <MWHPR07MB31027D1A7BA923114625A5F5C6460@MWHPR07MB3102.namprd07.prod.outlook.com> (raw)
Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Thomas Monjalon <thomas@monjalon.net> Date: 10/23/17 20:28 (GMT+05:30) To: Santosh Shukla <santosh.shukla@caviumnetworks.com> Cc: dev@dpdk.org, olivier.matz@6wind.com, jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com, anatoly.burakov@intel.com Subject: Re: [dpdk-dev] [PATCH v3 0/6] make dpdk iova aware
20/10/2017 14:31, Santosh Shukla:
> v3:
> Include v2 review comment and rebased on
> top of upstream tip commit:6b9ed026a8704
>
>
> v2:
> Include build fixes reported in patchworks.
Please fix checkpatch issues, thanks
Santosh>
[Excuse me for font and typo..Travelling and has limited access to internet]
IIRC, those checkpatch warning coming from legacy code base, not because of iova change.
Though I tried to address most in v2.. and left those which I wasn't quite sure..if you insist then will address them in v4 series.
Thanks
next reply other threads:[~2017-10-23 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 15:16 sshukla [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-05 10:31 [dpdk-dev] [PATCH v2 0/5] " Santosh Shukla
2017-10-20 12:31 ` [dpdk-dev] [PATCH v3 0/6] " Santosh Shukla
2017-10-23 14:58 ` Thomas Monjalon
2017-10-24 5:12 ` santosh
2017-10-24 7:38 ` Thomas Monjalon
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=MWHPR07MB31027D1A7BA923114625A5F5C6460@MWHPR07MB3102.namprd07.prod.outlook.com \
--to=sshukla@caviumnetworks.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=olivier.matz@6wind.com \
--cc=santosh.shukla@caviumnetworks.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).