From: Levend Sayar <levendsayar@gmail.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] build: C++ linkage support is added to rte_service_component.h file
Date: Tue, 7 Jul 2020 18:31:20 +0300 [thread overview]
Message-ID: <CAGDw98=+a5+TXp-f5t1j5dWFmtKMg7pz=pnznAysWZo=+QpKbg@mail.gmail.com> (raw)
In-Reply-To: <BYAPR11MB3143915B07941B0E4A4FEA75D7660@BYAPR11MB3143.namprd11.prod.outlook.com>
Sorry.
I thought that it does not need to have any explanation since it is obvious
as you said.
But will add an explanation right now and push again.
Thanks for your attention.
Best,
Levend
On Tue, Jul 7, 2020 at 6:01 PM Van Haaren, Harry <harry.van.haaren@intel.com>
wrote:
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Tuesday, July 7, 2020 3:19 PM
> > To: levendsayar@gmail.com
> > Cc: dev@dpdk.org; Van Haaren, Harry <harry.van.haaren@intel.com>;
> > david.marchand@redhat.com
> > Subject: Re: [PATCH] build: C++ linkage support is added to
> > rte_service_component.h file
> >
> > 07/07/2020 14:25, levendsayar@gmail.com:
> > > From: Levend Sayar <levendsayar@gmail.com>
> >
> > Would be good to have a short explanation, even if obvious.
>
> +1
>
> > > Signed-off-by: Levend Sayar <levendsayar@gmail.com>
>
> With a short description in the commit message, you can include ack in v2
> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
>
> <snip patch>
>
next prev parent reply other threads:[~2020-07-08 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 12:25 levendsayar
2020-07-07 14:19 ` Thomas Monjalon
2020-07-07 15:00 ` Van Haaren, Harry
2020-07-07 15:31 ` Levend Sayar [this message]
2020-07-09 12:32 ` [dpdk-dev] [PATCH v3] service: support C++ linkage levendsayar
2020-07-09 13:21 ` Thomas Monjalon
2020-07-09 13:56 ` Levend Sayar
2020-07-09 14:24 ` 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='CAGDw98=+a5+TXp-f5t1j5dWFmtKMg7pz=pnznAysWZo=+QpKbg@mail.gmail.com' \
--to=levendsayar@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.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).