All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Hogan <james.hogan@mips.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: linux-mips@linux-mips.org, sulrich@codeaurora.org, arnd@arndb.de,
	linux-arm-msm@vger.kernel.org, timur@codeaurora.org,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	Paul Burton <paul.burton@mips.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/2] MIPS: io: add a barrier after register read in readX()
Date: Wed, 11 Apr 2018 21:26:17 +0100	[thread overview]
Message-ID: <20180411202616.GA14760@jhogan-linux.mipstec.com> (raw)
In-Reply-To: <14a663f6-2ea5-230b-2cd0-e42d05d0d7ea@codeaurora.org>


[-- Attachment #1.1: Type: text/plain, Size: 143 bytes --]

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

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
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()
Date: Wed, 11 Apr 2018 21:26:17 +0100	[thread overview]
Message-ID: <20180411202616.GA14760@jhogan-linux.mipstec.com> (raw)
In-Reply-To: <14a663f6-2ea5-230b-2cd0-e42d05d0d7ea@codeaurora.org>

[-- Attachment #1: Type: text/plain, Size: 143 bytes --]

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
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()
Date: Wed, 11 Apr 2018 21:26:17 +0100	[thread overview]
Message-ID: <20180411202616.GA14760@jhogan-linux.mipstec.com> (raw)
Message-ID: <20180411202617.pK_teeheh5VxcaTKNAPBQxUFSKM5p7dF7iPlXT_b2js@z> (raw)
In-Reply-To: <14a663f6-2ea5-230b-2cd0-e42d05d0d7ea@codeaurora.org>

[-- Attachment #1: Type: text/plain, Size: 143 bytes --]

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: james.hogan@mips.com (James Hogan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] MIPS: io: add a barrier after register read in readX()
Date: Wed, 11 Apr 2018 21:26:17 +0100	[thread overview]
Message-ID: <20180411202616.GA14760@jhogan-linux.mipstec.com> (raw)
In-Reply-To: <14a663f6-2ea5-230b-2cd0-e42d05d0d7ea@codeaurora.org>

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180411/a68a6239/attachment.sig>

  reply	other threads:[~2018-04-11 20:26 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03 12:55 [PATCH v3 1/2] MIPS: io: prevent compiler reordering on the default writeX() implementation Sinan Kaya
2018-04-03 12:55 ` Sinan Kaya
2018-04-03 12:55 ` [PATCH v3 2/2] MIPS: io: add a barrier after register read in readX() Sinan Kaya
2018-04-03 12:55   ` Sinan Kaya
2018-04-06  1:34   ` Sinan Kaya
2018-04-06  1:34     ` Sinan Kaya
2018-04-06 18:15     ` Sinan Kaya
2018-04-06 18:15       ` Sinan Kaya
2018-04-06 21:26       ` James Hogan
2018-04-06 21:26         ` James Hogan
2018-04-07 21:43         ` Sinan Kaya
2018-04-07 21:43           ` Sinan Kaya
2018-04-11 17:10           ` Sinan Kaya
2018-04-11 17:10             ` Sinan Kaya
2018-04-11 20:26             ` James Hogan [this message]
2018-04-11 20:26               ` James Hogan
2018-04-11 20:26               ` James Hogan
2018-04-11 20:26               ` James Hogan
2018-04-11 20:48               ` Sinan Kaya
2018-04-11 20:48                 ` Sinan Kaya
2018-04-11 17:04         ` Maciej W. Rozycki
2018-04-11 17:04           ` Maciej W. Rozycki
2018-04-11 17:04           ` Maciej W. Rozycki
2018-04-11 17:04           ` Maciej W. Rozycki
2018-04-12 21:51   ` James Hogan
2018-04-12 21:51     ` James Hogan
2018-04-12 21:51     ` James Hogan
2018-04-12 21:58     ` James Hogan
2018-04-12 21:58       ` James Hogan
2018-04-12 22:38       ` Sinan Kaya
2018-04-12 22:38         ` Sinan Kaya
2018-04-12 22:20     ` Sinan Kaya
2018-04-12 22:20       ` Sinan Kaya
2018-04-13 15:41     ` David Laight
2018-04-13 15:41       ` David Laight
2018-04-13 16:36       ` Sinan Kaya
2018-04-13 16:36         ` Sinan Kaya
2018-04-13 16:36         ` Sinan Kaya

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=20180411202616.GA14760@jhogan-linux.mipstec.com \
    --to=james.hogan@mips.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=okaya@codeaurora.org \
    --cc=paul.burton@mips.com \
    --cc=ralf@linux-mips.org \
    --cc=sulrich@codeaurora.org \
    --cc=timur@codeaurora.org \
    /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.