From: Thomas Monjalon <thomas@monjalon.net>
To: Apeksha Gupta <apeksha.gupta@nxp.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"nipun.gupta@nxp.com" <nipun.gupta@nxp.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v3 1/2] app/test-eventdev: Fix pipeline atq
Date: Wed, 22 Jul 2020 09:48:07 +0200 [thread overview]
Message-ID: <1868278.mr0rtG75vS@thomas> (raw)
In-Reply-To: <BN6PR18MB1140F17780B8D753E1D5582FDE790@BN6PR18MB1140.namprd18.prod.outlook.com>
22/07/2020 03:13, Pavan Nikhilesh Bhagavatula:
>
> >Subject: [dpdk-dev] [PATCH v3 1/2] app/test-eventdev: Fix pipeline atq
>
> ./devtools/check-git-log.sh
> Wrong headline uppercase:
> app/test-eventdev: Fix pipeline atq
>
> Having a more informative commit title and message would be helpful,
> Something like:
>
> " app/eventdev: fix capability check in pipeline atq test"
What means "atq"?
If it is an acronym, it should be uppercased.
next prev parent reply other threads:[~2020-07-22 7:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 6:06 [dpdk-stable] [PATCH 1/6] app/test-eventdev: Enhancing perf-queue packet flow Apeksha Gupta
2020-07-01 6:06 ` [dpdk-stable] [PATCH 2/6] app/test-eventdev: Removed unwanted checks Apeksha Gupta
2020-07-01 6:06 ` [dpdk-stable] [PATCH 3/6] event/dpaa2: Add all type queue capability flag Apeksha Gupta
2020-07-01 6:06 ` [dpdk-stable] [PATCH 4/6] app/test-eventdev: Fix pipeline atq Apeksha Gupta
2020-07-10 13:08 ` [dpdk-stable] [PATCH v2] " Apeksha Gupta
2020-07-13 11:44 ` [dpdk-stable] [PATCH v3 1/2] " Apeksha Gupta
2020-07-13 11:44 ` [dpdk-stable] [PATCH v3 2/2] event/dpaa2: Add all type queue capability flag Apeksha Gupta
2020-07-21 17:51 ` [dpdk-stable] [dpdk-dev] " Jerin Jacob
2020-07-23 13:36 ` [dpdk-stable] " Nipun Gupta
2020-07-24 5:24 ` [dpdk-stable] [dpdk-dev] " Jerin Jacob
2020-07-23 17:04 ` [dpdk-stable] [PATCH v4 2/2] event/dpaa2: add " Apeksha Gupta
2020-07-22 1:13 ` [dpdk-stable] [dpdk-dev] [PATCH v3 1/2] app/test-eventdev: Fix pipeline atq Pavan Nikhilesh Bhagavatula
2020-07-22 7:48 ` Thomas Monjalon [this message]
2020-07-23 17:02 ` [dpdk-stable] [PATCH v4 1/2] app/test-eventdev: fix capability check in pipeline ATQ test Apeksha Gupta
2020-07-01 6:06 ` [dpdk-stable] [PATCH 5/6] app/test-eventdev: Enhancing perf-atq packet flow Apeksha Gupta
2020-07-02 3:25 ` [dpdk-stable] [dpdk-dev] " Pavan Nikhilesh Bhagavatula
2020-07-02 14:46 ` [dpdk-stable] [EXT] " Apeksha Gupta
2020-07-01 6:06 ` [dpdk-stable] [PATCH 6/6] app/test-eventdev: fix eventdev queues Apeksha Gupta
2020-07-02 3:27 ` [dpdk-stable] [dpdk-dev] " Pavan Nikhilesh Bhagavatula
2020-07-09 13:05 ` [dpdk-stable] [EXT] " Apeksha Gupta
2020-07-02 3:24 ` [dpdk-stable] [dpdk-dev] [PATCH 1/6] app/test-eventdev: Enhancing perf-queue packet flow Pavan Nikhilesh Bhagavatula
2020-07-02 14:46 ` [dpdk-stable] [EXT] " Apeksha Gupta
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=1868278.mr0rtG75vS@thomas \
--to=thomas@monjalon.net \
--cc=apeksha.gupta@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=nipun.gupta@nxp.com \
--cc=pbhagavatula@marvell.com \
--cc=stable@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 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).