From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: "Thomas Monjalon" <thomas@monjalon.net>,
"Akhil Goyal" <gakhil@marvell.com>, "ci@dpdk.org" <ci@dpdk.org>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
"Ajit Khaparde" <ajit.khaparde@broadcom.com>,
"Qi Zhang" <qi.z.zhang@intel.com>,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>,
"Raslan Darawsheh" <rasland@nvidia.com>,
"Maxime Coquelin" <maxime.coquelin@redhat.com>,
"Xia, Chenbo" <chenbo.xia@intel.com>,
"Luca Boccassi" <bluca@debian.org>,
"Kevin Traynor" <ktraynor@redhat.com>,
"Christian Ehrhardt" <christian.ehrhardt@canonical.com>,
"Xueming(Steven) Li" <xuemingl@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"Bruce Richardson" <bruce.richardson@intel.com>,
"Michael Santana" <maicolgabriel@hotmail.com>,
"Abdullah Ömer Yamaç" <omer.yamac@ceng.metu.edu.tr>,
"Aaron Conole" <aconole@redhat.com>
Subject: Re: [EXT] Re: [PATCH v4 1/2] drivers: fix symbol exports when map is omitted
Date: Tue, 6 Dec 2022 11:18:07 +0100 [thread overview]
Message-ID: <CAJFAV8zRLq9rcXYR+WKnSL2py3jzREEBmTQH3T4tnA=aMOY=-A@mail.gmail.com> (raw)
In-Reply-To: <734b4cca-331a-9a6e-8300-3bf024e326d9@amd.com>
On Tue, Dec 6, 2022 at 11:13 AM Ferruh Yigit <ferruh.yigit@amd.com> wrote:
> On 12/5/2022 3:37 PM, Thomas Monjalon wrote:
> > 05/12/2022 14:47, Akhil Goyal:
> >> But adding a tag on same repo is more convenient from developer point of view.
> >> However, it is my personal view, others may differ.
> >
> > From developer point of view, you should use devtools/test-meson-builds.sh
> > which does the "git clone" for you.
> >
> > This is what I have in ~/.config/dpdk/devel.config
> > export DPDK_ABI_REF_DIR=$root/dpdk-build/abiref
> > export DPDK_ABI_REF_VERSION=v22.11.1
> >
>
> Does it help to update 'test-meson-builds.sh' to use an environment
> variable to select which repo to clone?
> If so, I can send a patch for it.
I was wondering too...
I would expect most maintainers have the stable repo in their config
but it would not hurt to handle the case when they don't for others.
+1
--
David Marchand
next prev parent reply other threads:[~2022-12-06 10:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221129140032.35940-1-david.marchand@redhat.com>
[not found] ` <20221202110945.519708-1-david.marchand@redhat.com>
[not found] ` <f7t8rjpkjq7.fsf@redhat.com>
2022-12-05 10:23 ` David Marchand
2022-12-05 10:43 ` [EXT] " Akhil Goyal
2022-12-05 12:36 ` David Marchand
2022-12-05 13:47 ` Akhil Goyal
2022-12-05 15:37 ` Thomas Monjalon
2022-12-05 16:26 ` Akhil Goyal
2022-12-06 10:12 ` Ferruh Yigit
2022-12-06 10:18 ` David Marchand [this message]
2022-12-06 12:25 ` Ferruh Yigit
2022-12-07 18:00 ` Patrick Robb
2022-12-08 13:22 ` Thomas Monjalon
2022-12-08 16:06 ` Patrick Robb
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='CAJFAV8zRLq9rcXYR+WKnSL2py3jzREEBmTQH3T4tnA=aMOY=-A@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=chenbo.xia@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=ktraynor@redhat.com \
--cc=maicolgabriel@hotmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=omer.yamac@ceng.metu.edu.tr \
--cc=qi.z.zhang@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=xuemingl@nvidia.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).