patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Luca Boccassi <bluca@debian.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-stable] Please help fixing ARM64 on 18.02 stable branch
Date: Mon, 21 May 2018 13:03:51 +0000	[thread overview]
Message-ID: <HE1PR0402MB27800EE6962F8E79E4651FDD90950@HE1PR0402MB2780.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1526896785.23337.145.camel@debian.org>

Hello Luca

> -----Original Message-----
> From: Luca Boccassi [mailto:bluca@debian.org]
> Sent: Monday, May 21, 2018 3:30 PM
> To: Hemant Agrawal <hemant.agrawal@nxp.com>; Shreyansh Jain
> <shreyansh.jain@nxp.com>
> Cc: thomas@monjalon.net; stable@dpdk.org
> Subject: Please help fixing ARM64 on 18.02 stable branch
> 
> Hello,
> 
> Thomas found a build error in the DPAA2 PMD when cross-building to
> arm64, if you can could you please help us and provide a fix for the
> 18.02 stable branch?
> 
[..]

I have sent a patch to stable mailing list [1].
Hopefully this would fix the issue.
It seems that one of the stable CC'd patches (on dev ML) was not completely about stable and another was missed (as it contained things not intended for stable).

[1] http://dpdk.org/ml/archives/stable/2018-May/007156.html

-
Shreyansh

      parent reply	other threads:[~2018-05-21 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21  9:59 Luca Boccassi
2018-05-21 10:01 ` Shreyansh Jain
2018-05-21 10:11   ` Thomas Monjalon
2018-05-21 13:03 ` Shreyansh Jain [this message]

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=HE1PR0402MB27800EE6962F8E79E4651FDD90950@HE1PR0402MB2780.eurprd04.prod.outlook.com \
    --to=shreyansh.jain@nxp.com \
    --cc=bluca@debian.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=stable@dpdk.org \
    --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).