From: Neil Horman <nhorman@tuxdriver.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: fix ABI breakage in lro code
Date: Mon, 3 Aug 2015 08:53:03 -0400 [thread overview]
Message-ID: <20150803125303.GA13755@hmsreliant.think-freely.org> (raw)
In-Reply-To: <7256638.4inC2JWGiy@xps13>
On Mon, Aug 03, 2015 at 10:41:47AM +0200, Thomas Monjalon wrote:
> Chao,
> The original need was to check with the ABI checker tool that the ABI
> was not broken on POWER BE by this patch.
>
Yes, its not compilation thats the concern, its ABI compatibility.
Neil
>
> 2015-08-03 11:45, Chao Zhu:
> > Confirmed. It can compile on Power8 Big Endian.
> > Thank you!
> >
> > On 2015/8/3 10:39, Chao Zhu wrote:
> > >
> > > Really sorry for the delay.
> > > Originally, I thought the email was to asking the ABI checking tools
> > > on Power which I'm not so familiar with. So this took me some time to
> > > find solution. For Power little endian, the build is OK. I'll give
> > > feedback when I tried Big endian compilation.
>
> [...]
>
> > >>>>>> I presume the ABI checker stopped complaining about this with the
> > >>>>>> patch, yes?
> > >>>>> Hi Neil,
> > >>>>>
> > >>>>> Yes, I replied about that in the previous thread.
> > >>>>>
> > >>>> Thank you, I'll ack as soon as Chao confirms its not a problem on
> > >>>> ppc Neil
>
>
next prev parent reply other threads:[~2015-08-03 12:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 10:26 John McNamara
2015-07-13 10:42 ` Neil Horman
2015-07-13 10:46 ` Thomas Monjalon
2015-07-13 10:47 ` Mcnamara, John
2015-07-13 13:59 ` Neil Horman
2015-07-17 11:45 ` Mcnamara, John
2015-07-17 12:25 ` Neil Horman
2015-07-31 9:03 ` Mcnamara, John
2015-07-31 10:34 ` Neil Horman
2015-08-03 2:39 ` Chao Zhu
2015-08-03 3:45 ` Chao Zhu
2015-08-03 8:41 ` Thomas Monjalon
2015-08-03 12:53 ` Neil Horman [this message]
2015-07-16 22:22 ` Vlad Zolotarov
2015-08-02 21:06 ` 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=20150803125303.GA13755@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).