From: James Hogan <jhogan@kernel.org>
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: Fri, 6 Apr 2018 22:26:01 +0100 [thread overview]
Message-ID: <20180406212601.GA1730@saruman> (raw)
In-Reply-To: <b748fdcb-e09f-9fe3-dc74-30b6a7d40cbe@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Fri, Apr 06, 2018 at 02:15:57PM -0400, Sinan Kaya wrote:
> On 4/5/2018 9:34 PM, Sinan Kaya wrote:
> > Can we get these merged to 4.17?
> >
> > There was a consensus to fix the architectures having API violation issues.
> > https://www.mail-archive.com/netdev@vger.kernel.org/msg225971.html
> >
> >
>
> Any news on the MIPS front? Is this something that Arnd can merge? or does it have
> to go through the MIPS tree.
It needs some MIPS input really. I'll try and take a look soon. Thanks
for the nudge.
> It feels like the MIPS is dead since nobody replied to me in the last few weeks on
> a very important topic.
Not dead, just both maintainers heavily distracted by real life right
now (which sadly, for me at least, trumps this very important topic) and
doing the best they can given the circumstances.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-06 21:26 UTC|newest]
Thread overview: 16+ 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 ` [PATCH v3 2/2] MIPS: io: add a barrier after register read in readX() Sinan Kaya
2018-04-06 1:34 ` Sinan Kaya
2018-04-06 18:15 ` Sinan Kaya
2018-04-06 21:26 ` James Hogan [this message]
2018-04-07 21:43 ` Sinan Kaya
2018-04-11 17:10 ` Sinan Kaya
2018-04-11 20:26 ` James Hogan
2018-04-11 20:48 ` Sinan Kaya
2018-04-11 17:04 ` Maciej W. Rozycki
2018-04-12 21:51 ` James Hogan
2018-04-12 21:58 ` James Hogan
2018-04-12 22:38 ` Sinan Kaya
2018-04-12 22:20 ` Sinan Kaya
2018-04-13 15:41 ` David Laight
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=20180406212601.GA1730@saruman \
--to=jhogan@kernel.org \
--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 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).