From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>,
Thinh Tran <thinhtr@linux.vnet.ibm.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "drc@linux.vnet.ibm.com" <drc@linux.vnet.ibm.com>,
Dmitry Kozlyuk <dkozlyuk@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2] net/mlx5: fix CPU socket ID for Rx queue creation
Date: Thu, 10 Mar 2022 09:30:52 +0000 [thread overview]
Message-ID: <BYAPR12MB307879EF191B082C5F14E9A5CF0B9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DM6PR12MB3753FE3392788E84D5B19622DF0B9@DM6PR12MB3753.namprd12.prod.outlook.com>
Hi,
> -----Original Message-----
> From: Slava Ovsiienko <viacheslavo@nvidia.com>
> Sent: Thursday, March 10, 2022 11:23 AM
> To: Thinh Tran <thinhtr@linux.vnet.ibm.com>; dev@dpdk.org
> Cc: drc@linux.vnet.ibm.com; Raslan Darawsheh <rasland@nvidia.com>;
> Dmitry Kozlyuk <dkozlyuk@nvidia.com>; stable@dpdk.org
> Subject: RE: [PATCH v2] net/mlx5: fix CPU socket ID for Rx queue creation
>
> Hi, Thinh
>
> the line: "v2: change patch description, no code change"
> should not be in commit message body, it should be after "---"
I'll handle this before integration,
It's also missing the Ack from Matan from the previous version, I'll add it as well.
> Besides this:
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
>
> With best regards,
> Slava
>
Kindest regards
Raslan Darawsheh
next prev parent reply other threads:[~2022-03-10 9:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 22:52 [PATCH] net/mlx5: set correct CPU socket ID for mlx5_rxq_ctrl Thinh Tran
2022-03-08 10:23 ` Matan Azrad
2022-03-08 12:14 ` Raslan Darawsheh
2022-03-08 12:23 ` Dmitry Kozlyuk
2022-03-08 12:25 ` Raslan Darawsheh
2022-03-09 8:50 ` Slava Ovsiienko
2022-03-09 17:10 ` Thinh Tran
2022-03-09 19:49 ` [PATCH v2] net/mlx5: fix CPU socket ID for Rx queue creation Thinh Tran
2022-03-10 9:23 ` Slava Ovsiienko
2022-03-10 9:30 ` Raslan Darawsheh [this message]
2022-03-10 15:38 ` Raslan Darawsheh
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=BYAPR12MB307879EF191B082C5F14E9A5CF0B9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=dkozlyuk@nvidia.com \
--cc=drc@linux.vnet.ibm.com \
--cc=stable@dpdk.org \
--cc=thinhtr@linux.vnet.ibm.com \
--cc=viacheslavo@nvidia.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 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.