From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 0/6] atomics: generate atomic headers / instrument arm64
Date: Fri, 19 Oct 2018 11:27:16 +0100 [thread overview]
Message-ID: <20181019102715.GA14246@arm.com> (raw)
In-Reply-To: <20181008171523.rw34hyaqap2yb3py@lakrids.cambridge.arm.com>
Hi Ingo,
On Mon, Oct 08, 2018 at 06:15:24PM +0100, Mark Rutland wrote:
> On Tue, Sep 04, 2018 at 11:48:24AM +0100, Mark Rutland wrote:
> > As previously requested, this is a (trivial) rebase of the remaining generated
> > atomic patches atop of v4.19-rc2, avoiding any potential conflict with Peter's
> > ldsem atomic cleanup patch that got taken through the tty tree.
> >
> > Are you still happy to pick this up? Full blurb below.
>
> Ping!
>
> Do you have any comments, or would you be happy to queue this?
>
> I'm happy to resend come rc1, if you'd prefer?
It would be really nice to see this merged. Any chance we could get this
queued at -rc1 for 4.21, please? If not, what more needs to be done?
Cheers,
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Mark Rutland <mark.rutland@arm.com>, mingo@kernel.org
Cc: arnd@arndb.de, aryabinin@virtuozzo.com, boqun.feng@gmail.com,
catalin.marinas@arm.com, dvyukov@google.com, glider@google.com,
linuxdrivers@attotech.com, linux-kernel@vger.kernel.org,
peterz@infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv3 0/6] atomics: generate atomic headers / instrument arm64
Date: Fri, 19 Oct 2018 11:27:16 +0100 [thread overview]
Message-ID: <20181019102715.GA14246@arm.com> (raw)
In-Reply-To: <20181008171523.rw34hyaqap2yb3py@lakrids.cambridge.arm.com>
Hi Ingo,
On Mon, Oct 08, 2018 at 06:15:24PM +0100, Mark Rutland wrote:
> On Tue, Sep 04, 2018 at 11:48:24AM +0100, Mark Rutland wrote:
> > As previously requested, this is a (trivial) rebase of the remaining generated
> > atomic patches atop of v4.19-rc2, avoiding any potential conflict with Peter's
> > ldsem atomic cleanup patch that got taken through the tty tree.
> >
> > Are you still happy to pick this up? Full blurb below.
>
> Ping!
>
> Do you have any comments, or would you be happy to queue this?
>
> I'm happy to resend come rc1, if you'd prefer?
It would be really nice to see this merged. Any chance we could get this
queued at -rc1 for 4.21, please? If not, what more needs to be done?
Cheers,
Will
next prev parent reply other threads:[~2018-10-19 10:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 10:48 [PATCHv3 0/6] atomics: generate atomic headers / instrument arm64 Mark Rutland
2018-09-04 10:48 ` Mark Rutland
2018-09-04 10:48 ` [PATCHv3 1/6] atomics: add common header generation files Mark Rutland
2018-09-04 10:48 ` Mark Rutland
2018-11-01 9:54 ` [tip:locking/core] locking/atomics: Add " tip-bot for Mark Rutland
2018-11-01 10:06 ` tip-bot for Mark Rutland
2018-11-15 23:03 ` [PATCHv3 1/6] atomics: add " Andrew Morton
2018-11-15 23:03 ` Andrew Morton
2018-11-15 23:10 ` Andrew Morton
2018-11-15 23:10 ` Andrew Morton
2018-11-16 2:51 ` Mark Rutland
2018-11-16 2:51 ` Mark Rutland
2018-11-21 22:34 ` Andrew Morton
2018-11-21 22:34 ` Andrew Morton
2018-09-04 10:48 ` [PATCHv3 2/6] atomics: switch to generated fallbacks Mark Rutland
2018-09-04 10:48 ` Mark Rutland
2018-11-01 9:55 ` [tip:locking/core] locking/atomics: Switch " tip-bot for Mark Rutland
2018-11-01 10:07 ` tip-bot for Mark Rutland
2018-09-04 10:48 ` [PATCHv3 3/6] atomics: switch to generated atomic-long Mark Rutland
2018-09-04 10:48 ` Mark Rutland
2018-11-01 9:55 ` [tip:locking/core] locking/atomics: Switch " tip-bot for Mark Rutland
2018-11-01 10:08 ` tip-bot for Mark Rutland
2018-09-04 10:48 ` [PATCHv3 4/6] atomics: switch to generated instrumentation Mark Rutland
2018-09-04 10:48 ` Mark Rutland
2018-11-01 9:56 ` [tip:locking/core] locking/atomics: Switch " tip-bot for Mark Rutland
2018-11-01 10:08 ` tip-bot for Mark Rutland
2018-09-04 10:48 ` [PATCHv3 5/6] atomics: check generated headers are up-to-date Mark Rutland
2018-09-04 10:48 ` Mark Rutland
2018-11-01 9:57 ` [tip:locking/core] locking/atomics: Check " tip-bot for Mark Rutland
2018-11-01 10:09 ` tip-bot for Mark Rutland
2018-11-21 8:02 ` Ingo Molnar
2018-11-21 11:40 ` Mark Rutland
2018-11-28 8:30 ` Ingo Molnar
2018-09-04 10:48 ` [PATCHv3 6/6] arm64: use instrumented atomics Mark Rutland
2018-09-04 10:48 ` Mark Rutland
2018-11-01 9:57 ` [tip:locking/core] arm64: Use " tip-bot for Mark Rutland
2018-11-01 10:09 ` [tip:locking/core] arm64, locking/atomics: " tip-bot for Mark Rutland
2018-10-08 17:15 ` [PATCHv3 0/6] atomics: generate atomic headers / instrument arm64 Mark Rutland
2018-10-08 17:15 ` Mark Rutland
2018-10-19 10:27 ` Will Deacon [this message]
2018-10-19 10:27 ` Will Deacon
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=20181019102715.GA14246@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.