From: Bruce Richardson <bruce.richardson@intel.com>
To: Abdullah Sevincer <abdullah.sevincer@intel.com>
Cc: <dev@dpdk.org>, <jerinj@marvell.com>,
<mike.ximing.chen@intel.com>, <tirthendu.sarkar@intel.com>,
<pravin.pathak@intel.com>, <shivani.doneria@intel.com>
Subject: Re: [PATCH v4 0/3] DLB2 Enhancements
Date: Thu, 2 May 2024 08:34:25 +0100 [thread overview]
Message-ID: <ZjNCARBf3Dw7ORsX@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20240501194620.1199357-1-abdullah.sevincer@intel.com>
On Wed, May 01, 2024 at 02:46:17PM -0500, Abdullah Sevincer wrote:
> This patchset addresses DLB enhancements in the DLB driver.
>
> Abdullah Sevincer (3):
> event/dlb2: add support for HW delayed token
> event/dlb2: add support for dynamic HL entries
> event/dlb2: enhance DLB credit handling
>
Hi Abdullah,
Couple of small asks/tips when sending new versions of a patchset:
1) When sending v2, v3, v4 using git-send-email, include
"--in-reply-to <message-id-of-v1-cover-letter>" in the command. This will
ensure all copies of the patches get put in the same email thread, rather
than having different versions spread throughout the reader's mailbox.
2) Please include in the cover letter a short one/two-line description of
what has changed in each version, so anyone reviewing e.g. v4 after
reading v3, is aware of what parts of v4 they need to look at
specifically. Generally, this should be in reverse order e.g.
v4: renamed bar to foobar
v3: changed foo to bar
v2: added new foo
Thanks,
/Bruce
next prev parent reply other threads:[~2024-05-02 7:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 19:46 Abdullah Sevincer
2024-05-01 19:46 ` [PATCH v4 1/3] event/dlb2: add support for HW delayed token Abdullah Sevincer
2024-05-27 15:19 ` Jerin Jacob
2024-05-01 19:46 ` [PATCH v4 2/3] event/dlb2: add support for dynamic HL entries Abdullah Sevincer
2024-05-27 15:23 ` Jerin Jacob
2024-05-01 19:46 ` [PATCH v4 3/3] event/dlb2: enhance DLB credit handling Abdullah Sevincer
2024-05-27 15:30 ` Jerin Jacob
2024-05-02 7:34 ` Bruce Richardson [this message]
2024-05-02 15:52 ` [PATCH v4 0/3] DLB2 Enhancements Sevincer, Abdullah
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=ZjNCARBf3Dw7ORsX@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=abdullah.sevincer@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mike.ximing.chen@intel.com \
--cc=pravin.pathak@intel.com \
--cc=shivani.doneria@intel.com \
--cc=tirthendu.sarkar@intel.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).