From: "Hunt, David" <david.hunt@intel.com>
To: Omer Yamac <omer.yamac@ceng.metu.edu.tr>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH v2] examples/distributor: update dynamic configuration
Date: Fri, 2 Sep 2022 09:37:31 +0100 [thread overview]
Message-ID: <68db4214-e665-caee-36be-c6a4821a1136@intel.com> (raw)
In-Reply-To: <280448dcd62dc2fc16f3f6907e52d728@ceng.metu.edu.tr>
On 02/09/2022 06:20, Omer Yamac wrote:
> Hi David,
>
> I applied the changes as new version (v3), Thank you
>
--snip--
>> With the above suggested changes to the commit message:
>>
>> Reviewed-by: David Hunt <david.hunt@intel.com>
Hi Omer,
2 things:
Usually you submit subsequent versions of patches "in-reply-to" the
previous versions to keep them together. Please see other examples of
this on the mailing list.
It is normal to include any Reviewed-by or Acked-by tags in subsequent
versions if the patch has not changed significantly.
Rgds,
Dave.
next prev parent reply other threads:[~2022-09-02 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 21:13 [PATCH] examples/distributor: update dynamic configuration Abdullah Ömer Yamaç
2022-06-28 19:54 ` [PATCH v2] " Abdullah Ömer Yamaç
2022-09-01 10:58 ` Hunt, David
2022-09-02 5:20 ` Omer Yamac
2022-09-02 8:37 ` Hunt, David [this message]
2022-09-01 14:09 ` [PATCH v3] " Abdullah Ömer Yamaç
2022-09-02 9:12 ` Hunt, David
2022-10-31 15:03 ` Thomas Monjalon
2022-11-24 20:05 ` [PATCH v4] examples/distributor: remove dead code and renaming Rx,Tx Abdullah Ömer Yamaç
2022-11-24 20:17 ` [PATCH v5] " Abdullah Ömer Yamaç
2022-11-24 20:22 ` [PATCH v6] " Abdullah Ömer Yamaç
2022-11-24 20:31 ` [PATCH v7] " Abdullah Ömer Yamaç
-- strict thread matches above, loose matches on Subject: below --
2022-06-28 19:37 [PATCH v2] examples/distributor: update dynamic configuration Abdullah Ömer Yamaç
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=68db4214-e665-caee-36be-c6a4821a1136@intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=omer.yamac@ceng.metu.edu.tr \
--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 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.