From: Ingo Molnar <mingo@kernel.org>
To: Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
linux-arm-kernel@lists.infradead.org, Jeremy.Linton@arm.com,
longman@redhat.com, boqun.feng@gmail.com,
paulmck@linux.vnet.ibm.com
Subject: Re: [PATCH v3 0/5] Switch arm64 over to qrwlock
Date: Tue, 24 Oct 2017 17:40:45 +0200 [thread overview]
Message-ID: <20171024154045.zr7u4puc7xa25cgu@gmail.com> (raw)
In-Reply-To: <20171024144810.GD14568@arm.com>
* Will Deacon <will.deacon@arm.com> wrote:
> Ingo, Peter,
>
> Would you be willing to merge this via -tip, please? I'm happy to
> rebase/repost as required, but the code is in good shape now.
Sure, will do it tomorrow!
Thanks,
Ingo
next prev parent reply other threads:[~2017-10-24 15:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 12:20 Will Deacon
2017-10-12 12:20 ` [PATCH v3 1/5] kernel/locking: Use struct qrwlock instead of struct __qrwlock Will Deacon
2017-10-25 10:13 ` [tip:locking/core] locking/qrwlock: Use 'struct qrwlock' instead of 'struct __qrwlock' tip-bot for Will Deacon
2017-10-12 12:20 ` [PATCH v3 2/5] locking/atomic: Add atomic_cond_read_acquire Will Deacon
2017-10-25 10:14 ` [tip:locking/core] locking/atomic: Add atomic_cond_read_acquire() tip-bot for Will Deacon
2017-10-12 12:20 ` [PATCH v3 3/5] kernel/locking: Use atomic_cond_read_acquire when spinning in qrwlock Will Deacon
2017-10-25 10:14 ` [tip:locking/core] locking/qrwlock: Use atomic_cond_read_acquire() " tip-bot for Will Deacon
2017-10-12 12:20 ` [PATCH v3 4/5] arm64: locking: Move rwlock implementation over to qrwlocks Will Deacon
2017-10-25 10:14 ` [tip:locking/core] locking/qrwlock, arm64: " tip-bot for Will Deacon
2017-10-12 12:20 ` [PATCH v3 5/5] kernel/locking: Prevent slowpath writers getting held up by fastpath Will Deacon
2017-10-25 10:15 ` [tip:locking/core] locking/qrwlock: " tip-bot for Will Deacon
2017-10-12 13:16 ` [PATCH v3 0/5] Switch arm64 over to qrwlock Adam Wallis
2017-10-19 16:53 ` Will Deacon
2017-10-24 14:48 ` Will Deacon
2017-10-24 15:40 ` Ingo Molnar [this message]
2017-10-25 8:36 ` Peter Zijlstra
2017-10-28 6:10 ` chengjian (D)
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=20171024154045.zr7u4puc7xa25cgu@gmail.com \
--to=mingo@kernel.org \
--cc=Jeremy.Linton@arm.com \
--cc=boqun.feng@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.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
Powered by JetHome