DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yutang Jiang <yutang.jiang@amperecomputing.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>,
	Yutang Jiang OS <jiangyutang@os.amperecomputing.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Open Source Submission <patches@amperecomputing.com>,
	"nd@arm.com" <nd@arm.com>,
	"juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>,
	"wathsala.vithanage@arm.com" <wathsala.vithanage@arm.com>
Subject: RE: [PATCH v2] config/arm: add Ampere AmpereOneX platform
Date: Thu, 27 Jun 2024 02:53:43 +0000	[thread overview]
Message-ID: <CH3PR01MB8594CEF1DEAF0D4097792AA19ED72@CH3PR01MB8594.prod.exchangelabs.com> (raw)
In-Reply-To: <897601ef-7a7f-4d4a-970c-4e2b06e3c1a7@arm.com>

Thank you, Ruifeng.
I noticed that variable patch, and have updated and submitted a new v3 patch.

> -----Original Message-----
> From: Ruifeng Wang <Ruifeng.Wang@arm.com>
> Sent: Thursday, June 20, 2024 4:41 PM
> To: Yutang Jiang OS <jiangyutang@os.amperecomputing.com>;
> dev@dpdk.org
> Cc: Open Source Submission <patches@amperecomputing.com>; Yutang Jiang
> <yutang.jiang@amperecomputing.com>; nd@arm.com;
> juraj.linkes@pantheon.tech; wathsala.vithanage@arm.com
> Subject: Re: [PATCH v2] config/arm: add Ampere AmpereOneX platform
> 
> [EXTERNAL EMAIL NOTICE: This email originated from an external sender.
> Please be mindful of safe email handling and proprietary information
> protection practices.]
> 
> 
> On 2024/4/11 5:23 PM, Yutang Jiang wrote:
> > Signed-off-by: Yutang Jiang <jiangyutang@os.amperecomputing.com>
> > ---
> >   config/arm/arm64_ampereonex_linux_gcc | 16 ++++++++++++++++
> >   config/arm/meson.build                | 19 +++++++++++++++++++
> >   2 files changed, 35 insertions(+)
> >   create mode 100644 config/arm/arm64_ampereonex_linux_gcc
> >
> > diff --git a/config/arm/arm64_ampereonex_linux_gcc
> > b/config/arm/arm64_ampereonex_linux_gcc
> > new file mode 100644
> > index 0000000000..c5c334fdb7
> > --- /dev/null
> > +++ b/config/arm/arm64_ampereonex_linux_gcc
> > @@ -0,0 +1,16 @@
> > +[binaries]
> > +c = ['ccache', 'aarch64-linux-gnu-gcc'] cpp = ['ccache',
> > +'aarch64-linux-gnu-g++'] ar = 'aarch64-linux-gnu-gcc-ar'
> > +strip = 'aarch64-linux-gnu-strip'
> > +pkgconfig = 'aarch64-linux-gnu-pkg-config'
> 
> This variable is changed to remove some meson warning [1]. Please update
> accordingly.
> 
> With suggested change:
> Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
> 
> PS: you can take received ack from the previous version.
> 
> [1]
> https://patches.dpdk.org/project/dpdk/patch/20240617151458.1005103-
> 1-david.marchand@redhat.com/
> 
> Thanks.
> > +pcap-config = ''
> > +
> > +[host_machine]
> <snip>

      reply	other threads:[~2024-06-27  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  9:23 Yutang Jiang
2024-06-19 19:43 ` Thomas Monjalon
2024-06-27  3:03   ` Yutang Jiang
2024-06-20  8:40 ` Ruifeng Wang
2024-06-27  2:53   ` Yutang Jiang [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=CH3PR01MB8594CEF1DEAF0D4097792AA19ED72@CH3PR01MB8594.prod.exchangelabs.com \
    --to=yutang.jiang@amperecomputing.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=dev@dpdk.org \
    --cc=jiangyutang@os.amperecomputing.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=nd@arm.com \
    --cc=patches@amperecomputing.com \
    --cc=wathsala.vithanage@arm.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).