From: David Marchand <david.marchand@redhat.com>
To: Michael Santana <msantana@redhat.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] eal: sort experimental symbols per release
Date: Sat, 27 Jul 2019 09:17:09 +0200 [thread overview]
Message-ID: <CAJFAV8xmEAoB335en9CBtwvZmtPde=ptJUEgcHKONUhU1JBVsA@mail.gmail.com> (raw)
In-Reply-To: <c32db03f-a8eb-1cf8-575d-dbc72c3a6444@redhat.com>
On Fri, Jul 26, 2019 at 6:06 PM Michael Santana Francisco
<msantana@redhat.com> wrote:
>
> On 7/26/19 10:06 AM, David Marchand wrote:
>
> Sort the experimental symbols per release to make it easier/quicker to
> check for how long we have them.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> Changelog since v1:
> - rte_service symbols who got promoted to stable got reintroduced in
> experimental when rebasing this patch on master
>
> Just going off Stephen's original proposal; it should be sorted by release and then by alphabetical order. Some blocks weren't sorted by alphabetical order when I ran sort after I applied your patch
Ah yes, I had moved some blocks as is without checking them.
Fixed in v3.
Thanks!
--
David Marchand
next prev parent reply other threads:[~2019-07-27 7:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 13:51 [dpdk-dev] [PATCH] eal: order " David Marchand
2019-07-26 14:02 ` David Marchand
2019-07-26 14:06 ` [dpdk-dev] [PATCH v2] eal: sort " David Marchand
2019-07-26 14:54 ` David Marchand
2019-07-26 15:04 ` Ferruh Yigit
2019-07-26 16:06 ` Michael Santana Francisco
2019-07-27 7:17 ` David Marchand [this message]
2019-07-27 7:21 ` [dpdk-dev] [PATCH v3] " David Marchand
2019-07-29 15:10 ` Michael Santana Francisco
2019-07-29 20:26 ` 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='CAJFAV8xmEAoB335en9CBtwvZmtPde=ptJUEgcHKONUhU1JBVsA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=msantana@redhat.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).