DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jeremy Plsek <jplsek@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Vamsi Attunuru <vattunuru@marvell.com>, dev <dev@dpdk.org>,
	 Bruce Richardson <bruce.richardson@intel.com>,
	Aaron Conole <aconole@redhat.com>,
	taox.zhu@intel.com,
	 Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] mempool/octeontx2: fix compile issue
Date: Mon, 17 Feb 2020 13:04:44 -0500	[thread overview]
Message-ID: <CA+xUZB6t3CJTx5ZBNwRV3fKVKkZsgZ0hi98fhKhO9TqS2bhi=Q@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8zUUQFt0iZ0N0rn68QLiKQSrJGmXSTN8i07koGzUH7_VA@mail.gmail.com>

On Mon, Feb 17, 2020 at 9:57 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> Jeremy,
>
> On Mon, Feb 17, 2020 at 12:19 PM David Marchand
> <david.marchand@redhat.com> wrote:
> >
> > This patch has been sent with a date in the future.
> > Date: Mon, 17 Feb 2020 16:43:45 +0000
> >
> > Please fix your mail setup, this triggers an error with meson in UNH
> > CI (at least).
>
> Do you use the tools/pwclient script from dpdk-ci or some git-am
> script of yours?

We use a customized script given to us by the Intel CI team which does
use git-am.

> I can see git-am has an option to tweak the commit dates (--ignore-date).

I can look into adding it.

I've also updated our compile scripts (again) to hopefully mitigate
the issue. I've also rerun the tests for this patch with those
changes.
>
> This should avoid the issue of files in the future that meson is not happy with.
>
>
> --
> David Marchand
>


-- 
Jeremy Plsek
UNH InterOperability Laboratory

  reply	other threads:[~2020-02-17 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 16:43 taox.zhu
2020-02-17 11:19 ` David Marchand
2020-02-17 14:57   ` David Marchand
2020-02-17 18:04     ` Jeremy Plsek [this message]
2020-02-17 18:28       ` Thomas Monjalon
2020-02-17 13:06 ` Jerin Jacob
2020-02-17 14:57   ` David Marchand
2020-02-17 18:29   ` 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='CA+xUZB6t3CJTx5ZBNwRV3fKVKkZsgZ0hi98fhKhO9TqS2bhi=Q@mail.gmail.com' \
    --to=jplsek@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=taox.zhu@intel.com \
    --cc=vattunuru@marvell.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).