DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mokhtar, Amr" <amr.mokhtar@intel.com>
To: "Chalupnik, KamilX" <kamilx.chalupnik@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] baseband/turbo_sw: internal buffers names changed
Date: Thu, 24 May 2018 10:25:10 +0000	[thread overview]
Message-ID: <3D3765A8CDB52A4C8B410430AA19CB236ECE03D4@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <20180524092017.12464-1-kamilx.chalupnik@intel.com>


> -----Original Message-----
> From: Chalupnik, KamilX
> Sent: Thursday 24 May 2018 10:20
> To: dev@dpdk.org
> Cc: Mokhtar, Amr <amr.mokhtar@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Chalupnik, KamilX
> <kamilx.chalupnik@intel.com>
> Subject: [PATCH v2] baseband/turbo_sw: internal buffers names changed
> 
> Internal buffers names have been shortened to meet ring names size
> requirements after device name changed.
> 
> Signed-off-by: Kamil Chalupnik <kamilx.chalupnik@intel.com>
> ---

It should have "Fixes: XXX" tag because it is a fix for a previous patch.
But the fix itself is ok with me.
Feel free to retain my "Acked-by" tag in the next patch when you add the "Fixes" tag

Acked-by: Amr Mokhtar <amr.mokhtar@intel.com>

  reply	other threads:[~2018-05-24 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24  7:46 [dpdk-dev] [PATCH] " Kamil Chalupnik
2018-05-24  9:20 ` [dpdk-dev] [PATCH v2] " Kamil Chalupnik
2018-05-24 10:25   ` Mokhtar, Amr [this message]
2018-05-24 12:41   ` [dpdk-dev] [PATCH v3] " Kamil Chalupnik
2018-05-28  1:19     ` 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=3D3765A8CDB52A4C8B410430AA19CB236ECE03D4@IRSMSX104.ger.corp.intel.com \
    --to=amr.mokhtar@intel.com \
    --cc=dev@dpdk.org \
    --cc=kamilx.chalupnik@intel.com \
    --cc=pablo.de.lara.guarch@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).