From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH v5 00/29] introduce I/O device memory
	read/write operations
Date: Wed, 18 Jan 2017 10:56:57 +0100
Message-ID: <3139214.lXrbRuBdqr@xps13>
References: <1484637244-7548-1-git-send-email-jerin.jacob@caviumnetworks.com>
 <1484702502-25451-1-git-send-email-jerin.jacob@caviumnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org, konstantin.ananyev@intel.com, bruce.richardson@intel.com,
 jianbo.liu@linaro.org, viktorin@rehivetech.com,
 santosh.shukla@caviumnetworks.com
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com
 [209.85.215.42]) by dpdk.org (Postfix) with ESMTP id 2F019F932
 for <dev@dpdk.org>; Wed, 18 Jan 2017 10:56:59 +0100 (CET)
Received: by mail-lf0-f42.google.com with SMTP id z134so6433371lff.3
 for <dev@dpdk.org>; Wed, 18 Jan 2017 01:56:59 -0800 (PST)
In-Reply-To: <1484702502-25451-1-git-send-email-jerin.jacob@caviumnetworks.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2017-01-18 06:51, Jerin Jacob:
> v5:
> 1) net/ena: removed intermediate readl/writel implementation and
> implemented ENA_REG_READ32/ENA_REG_WRITE32 as rte_read_relaxed/
> rte_write32_relaxed(Jan Medala)
> 2) Rebased to dpdk.org master
> 3) Created a temporary branch in public repo to share changes for easy testing
> 
> repo: https://github.com/jerinjacobk/dpdk.git
> branch: rte_io_v5

I will apply it on top of next-net in order to have it in 17.02-rc1.
Any objection?

Please could you check there is no rebase issue on top of next-net?
RC1 is expected today.