DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Michal Krawczyk <mk@semihalf.com>, dev@dpdk.org
Cc: gtzalik@amazon.com, mw@semihalf.com, matua@amazon.com,
	mba@semihalf.com, igorch@amazon.com
Subject: Re: [dpdk-dev] [PATCH v2 1/2] net/ena: upgrade HAL for new HW features
Date: Fri, 10 Jan 2020 09:04:39 +0000	[thread overview]
Message-ID: <037cf6f5-2e39-2cfb-678d-cba1dfd72e86@intel.com> (raw)
In-Reply-To: <20200109153912.5263-1-mk@semihalf.com>

On 1/9/2020 3:39 PM, Michal Krawczyk wrote:
> This version of the HAL allows to use the latest HW features, like
> rx offsets.
> 
> Driver was adjusted to the new version to fix the build.
> 
> Signed-off-by: Michal Krawczyk <mk@semihalf.com>
> Signed-off-by: Maciej Bielski <mba@semihalf.com>
> ---
> v2:
> * Fix compilation with debug options enabled by using PRIu64 for
>   printout variable type specifier

Hi Michał,

Next time can you please send the new versions as patchset, dealing with the
individual patches in patchets is difficult and error prone in this volume of
patches.
Also it breaks CI chekcs and some tooling like patchwork which supports series
(patchset).

Thanks,
ferruh

  reply	other threads:[~2020-01-10  9:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 13:32 [dpdk-dev] [PATCH 0/2] net/ena: add support for Rx offsets Michal Krawczyk
2019-12-13 13:32 ` [dpdk-dev] [PATCH 1/2] net/ena: upgrade HAL for new HW features Michal Krawczyk
2019-12-13 16:34   ` Stephen Hemminger
2019-12-13 20:01     ` Michał Krawczyk
2020-01-09 14:27       ` Ferruh Yigit
2020-01-09 15:26         ` Michał Krawczyk
2020-01-09 14:30   ` Ferruh Yigit
2020-01-09 15:39     ` [dpdk-dev] [PATCH v2 " Michal Krawczyk
2020-01-10  9:04       ` Ferruh Yigit [this message]
2020-01-10  9:39         ` Michał Krawczyk
2020-01-10 10:32       ` Ferruh Yigit
2019-12-13 13:32 ` [dpdk-dev] [PATCH 2/2] net/ena: add support for RX_OFFSET feature Michal Krawczyk
2020-01-10 10:32   ` Ferruh Yigit

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=037cf6f5-2e39-2cfb-678d-cba1dfd72e86@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=gtzalik@amazon.com \
    --cc=igorch@amazon.com \
    --cc=matua@amazon.com \
    --cc=mba@semihalf.com \
    --cc=mk@semihalf.com \
    --cc=mw@semihalf.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).