DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Xiao Wang <xiao.w.wang@intel.com>,
	"sthemmin@microsoft.com" <sthemmin@microsoft.com>,
	"shaopeng.he@intel.com" <shaopeng.he@intel.com>,
	"Jacob, Jerin" <Jerin.JacobKollanukkaran@cavium.com>
Subject: Re: [dpdk-dev] [dpdk-stable]  [PATCH v2 2/2] eal: fix build issue
Date: Mon, 12 Nov 2018 10:17:48 +0100	[thread overview]
Message-ID: <10884160.uktxByOJIo@xps> (raw)
In-Reply-To: <77bf925a-00b8-8a71-b9ca-0c8c76c94371@intel.com>

12/11/2018 10:01, Ferruh Yigit:
> On 11/12/2018 4:50 AM, Jerin Jacob wrote:
> > -----Original Message-----
> >> Date: Mon, 12 Nov 2018 02:37:15 +0100
> >> From: Thomas Monjalon <thomas@monjalon.net>
> >> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> >> Cc: stable@dpdk.org, "dev@dpdk.org" <dev@dpdk.org>, Qi Zhang
> >>  <qi.z.zhang@intel.com>, Xiao Wang <xiao.w.wang@intel.com>,
> >>  "sthemmin@microsoft.com" <sthemmin@microsoft.com>, "shaopeng.he@intel.com"
> >>  <shaopeng.he@intel.com>, "Jacob, Jerin"
> >>  <Jerin.JacobKollanukkaran@cavium.com>
> >> Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2 2/2] eal: fix build issue
> >>
> >>
> >> 07/11/2018 07:59, Jerin Jacob:
> >>>  drivers/net/fm10k/fm10k_ethdev.c       | 11 +++--------
> >>>  lib/librte_eal/common/rte_reciprocal.c | 17 +----------------
> >>>  2 files changed, 4 insertions(+), 24 deletions(-)
> >>
> >> This patch is corrupted, please check.
> > 
> > Looks like it is working, can you check from patchwork.
> > 
> > ➜ [j] $ pwclient get 47915
> > Saved patch to v2-1-2-eal-introduce-rte-version-of-fls
> > ➜ [j] $ pwclient get 47916
> > Saved patch to v2-2-2-eal-fix-build-issue
> > 
> > ➜ [master][dpdk.org] $ git am -3 /tmp/j/v2-*
> > Applying: eal: introduce rte version of fls
> > Applying: eal: fix build issue
> > 
> > ➜ [master]laptop [dpdk.org] $ echo $?
> > 0
> 
> Also works for me:
> $ git-pw series apply 2306

Works for me too :)

The issue I was raising is about the format of the email.
Patch 1 content encoding is quoted-printable and patch 2 is base64.

I think we should all set sendemail.transferEncoding = 8bit

  reply	other threads:[~2018-11-12  9:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 11:45 [dpdk-dev] [PATCH] " Jerin Jacob
2018-11-06 12:29 ` Thomas Monjalon
2018-11-06 13:31   ` Jerin Jacob
2018-11-06 20:27     ` Thomas Monjalon
2018-11-07  6:59 ` [dpdk-dev] [PATCH v2 1/2] eal: introduce rte version of fls Jerin Jacob
2018-11-07  6:59   ` [dpdk-dev] [PATCH v2 2/2] eal: fix build issue Jerin Jacob
2018-11-12  1:37     ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2018-11-12  4:50       ` Jerin Jacob
2018-11-12  9:01         ` Ferruh Yigit
2018-11-12  9:17           ` Thomas Monjalon [this message]
2018-11-12 12:28     ` 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=10884160.uktxByOJIo@xps \
    --to=thomas@monjalon.net \
    --cc=Jerin.JacobKollanukkaran@cavium.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=qi.z.zhang@intel.com \
    --cc=shaopeng.he@intel.com \
    --cc=stable@dpdk.org \
    --cc=sthemmin@microsoft.com \
    --cc=xiao.w.wang@intel.com \
    /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).