From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Andrew Rybchenko <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] rte_log: make rte_logs private
Date: Mon, 14 Sep 2020 09:37:36 -0700 [thread overview]
Message-ID: <20200914093736.256b02f8@hermes.lan> (raw)
In-Reply-To: <CAJFAV8y_yxOXAo5o4QUQoA6qFNYisOd+s_RSx6iGAG2iAbjThQ@mail.gmail.com>
On Mon, 14 Sep 2020 10:13:29 +0200
David Marchand <david.marchand@redhat.com> wrote:
> On Fri, Sep 4, 2020 at 1:05 AM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > As announced in earlier releases, rte_logs can now be made
> > internal to eal_common_log.
> >
> > Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> Same comment as before, the rte_log_dynamic_type struct fwd
> declaration can be removed from the rte_log.h header.
> I will fix it while applying.
>
>
Thanks
next prev parent reply other threads:[~2020-09-14 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 22:54 [dpdk-dev] [PATCH] rte_log: make rte_logs private Stephen Hemminger
2020-08-29 12:41 ` Andrew Rybchenko
2020-09-02 8:40 ` David Marchand
2020-09-02 14:49 ` Stephen Hemminger
2020-09-03 23:04 ` [dpdk-dev] [PATCH v2 0/2] rte_log: make internal structures private Stephen Hemminger
2020-09-03 23:04 ` [dpdk-dev] [PATCH v2 1/2] rte_log: take experimental tag off of rte_log_get_stream Stephen Hemminger
2020-09-14 8:12 ` David Marchand
2020-09-03 23:04 ` [dpdk-dev] [PATCH v2 2/2] rte_log: make rte_logs private Stephen Hemminger
2020-09-14 8:13 ` David Marchand
2020-09-14 16:37 ` Stephen Hemminger [this message]
2020-09-16 16:36 ` David Marchand
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=20200914093736.256b02f8@hermes.lan \
--to=stephen@networkplumber.org \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.