From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1757376AbeDKUmG (ORCPT <rfc822;w@1wt.eu>);
        Wed, 11 Apr 2018 16:42:06 -0400
Received: from 9pmail.ess.barracuda.com ([64.235.150.225]:57613 "EHLO
        9pmail.ess.barracuda.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1756129AbeDKUmE (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 11 Apr 2018 16:42:04 -0400
Date: Wed, 11 Apr 2018 21:26:17 +0100
From: James Hogan <james.hogan@mips.com>
To: Sinan Kaya <okaya@codeaurora.org>
CC: <linux-mips@linux-mips.org>, <arnd@arndb.de>, <timur@codeaurora.org>,
        <sulrich@codeaurora.org>, <linux-arm-msm@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>,
        Ralf Baechle <ralf@linux-mips.org>, Paul Burton <paul.burton@mips.com>,
        <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] MIPS: io: add a barrier after register read in
 readX()
Message-ID: <20180411202616.GA14760@jhogan-linux.mipstec.com>
References: <1522760109-16497-1-git-send-email-okaya@codeaurora.org>
 <1522760109-16497-2-git-send-email-okaya@codeaurora.org>
 <41e184ae-689e-93c9-7b15-0c68bd624130@codeaurora.org>
 <b748fdcb-e09f-9fe3-dc74-30b6a7d40cbe@codeaurora.org>
 <20180406212601.GA1730@saruman>
 <0f1a4719-9a6f-0df0-7fd9-a25c10e824f5@codeaurora.org>
 <14a663f6-2ea5-230b-2cd0-e42d05d0d7ea@codeaurora.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62"
Content-Disposition: inline
In-Reply-To: <14a663f6-2ea5-230b-2cd0-e42d05d0d7ea@codeaurora.org>
User-Agent: Mutt/1.7.2 (2016-11-26)
X-Originating-IP: [192.168.154.110]
X-ClientProxiedBy: mipsdag02.mipstec.com (10.20.40.47) To
 mipsdag02.mipstec.com (10.20.40.47)
X-BESS-ID: 1523479317-298552-17228-19489-1
X-BESS-VER: 2018.4-r1804052328
X-BESS-Apparent-Source-IP: 12.201.5.32
X-BESS-Outbound-Spam-Score: 0.00
X-BESS-Outbound-Spam-Report: Code version 3.2, rules version 3.2.2.191892
        Rule breakdown below
         pts rule name              description
        ---- ---------------------- --------------------------------
        0.00 BSF_BESS_OUTBOUND      META: BESS Outbound
X-BESS-Outbound-Spam-Status: SCORE=0.00 using account:ESS59374 scores of KILL_LEVEL=7.0 tests=BSF_BESS_OUTBOUND
X-BESS-BRTS-Status: 1
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

--+QahgC5+KEYLbs62
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline

On Wed, Apr 11, 2018 at 01:10:41PM -0400, Sinan Kaya wrote:
> How is the likelihood of getting this fixed on 4.17 kernel?

High.

Thanks
James

--+QahgC5+KEYLbs62
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEd80NauSabkiESfLYbAtpk944dnoFAlrOb2IACgkQbAtpk944
dnpn5w/+NdCeCbGpfWtq/05XIQr+5dP9M4Ehvlt/vrkLEpfPvsEQZJUgGcq1Pxta
k6Tx18KiNbH+CE1bo4za6it0bgPtVrMgMLICCNxtXQWoI73SpzMSoG6PVR7iaWmw
vlN9WA8uI4isfvVxXNdm/vayR1XpRLcRtrJ/jiNIcDxi9q5nwUTtXHXB1nnP8rFq
m67popm0z1mTcSPxRdGLyWv+bpbeJdap2Sl7cdt+vtY66h0gG3Fgli5Ux7Mjc56t
+EFbUZWSgCmxD+0dZIzXErxAc7mduOH8YU6N87QJz9YPGRebvYYcLkgTGE3Lk4t7
G2D+63vWYRlB168NdaIt0PTO6bWoSkRsC2Wmo7JobhD4tWzJKFFUgX21dwL0CcWx
Xb1EQgOa6n/eBh5SQikV0SsVjELNvcIXIf+pKNgH++fN9zZ/JMSW7wAm9FEv/0kh
wImtrz7Gh5Cx7GD9HVBTEa55T32DNOWliGUQW/E4pSJVexIUuV+VzZFovQq92qrZ
PYfmw2VmEznT8qHQEr1BMCSGqQp6sDYBzCgpym9UxYLW5qw9mhY4MwMr8wckl5Lz
eMR7cMdE+1luEpJgx/F/mVjbXBQv2sy7/Bgsb+c/01O07/9R1vTbDPpUczL2E3Zs
jSkZns8v0IzTzJtp5tyJRTWUdsqb2UzC2vWbNvrDg5us3chy2+8=
=TNbG
-----END PGP SIGNATURE-----

--+QahgC5+KEYLbs62--