From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>
Subject: Re: [dpdk-dev] [pull-request] next-pipeline 18.05 PRE-RC1
Date: Thu, 5 Apr 2018 11:00:10 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BB3B4B3@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <12703751.zyF59OW4Sh@xps>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Thursday, April 5, 2018 1:03 AM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org; Singh, Jasvinder <jasvinder.singh@intel.com>
> Subject: Re: [dpdk-dev] [pull-request] next-pipeline 18.05 PRE-RC1
>
> > > Hi,
> > >
> > > 30/03/2018 14:45, Cristian Dumitrescu:
> > > > http://dpdk.org/git/next/dpdk-next-pipeline
> > >
> > > I saw 2 issues:
> > > - table_index is wrongly placed in doxygen index
> > > - compilation error with clang: status_data is used uninitialized
> > >
> >
> > Hi Thomas,
> >
> > All the above issues are fixed now, are you OK to resume the pull request
> now?
>
> Sorry, one more compilation error:
>
> error: incompatible pointer types
> passing 'uint8_t *' (aka 'unsigned char *') to parameter of type 'uint32_t
> *'
> (aka 'unsigned int *') [-Werror,-Wincompatible-pointer-types]
> if (parser_read_uint32(&p.tc_ov_weight, tokens[10]) != 0) {
> ^~~~~~~~~~~~~~~
>
>
Fixed, sorry about this.
next prev parent reply other threads:[~2018-04-05 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 12:45 Cristian Dumitrescu
2018-04-04 7:53 ` Thomas Monjalon
2018-04-04 10:47 ` Dumitrescu, Cristian
2018-04-05 0:03 ` Thomas Monjalon
2018-04-05 11:00 ` Dumitrescu, Cristian [this message]
2018-04-06 16:45 ` 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=3EB4FA525960D640B5BDFFD6A3D891267BB3B4B3@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.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).