From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 6/7] arm64, jump label: optimize jump label implementation
Date: Wed, 8 Jan 2014 15:41:36 +0000 [thread overview]
Message-ID: <20140108154136.GD15212@arm.com> (raw)
In-Reply-To: <20140108110831.GA20644@mudshark.cambridge.arm.com>
On Wed, Jan 08, 2014 at 11:08:32AM +0000, Will Deacon wrote:
> On Wed, Jan 08, 2014 at 11:06:26AM +0000, Jiang Liu wrote:
> > Who should I send this patch set for merging?
>
> Catalin and I will pick up it from here and take it via the arm64 tree, so
> you don't need to do anything.
Done. It should appear in linux-next overnight (Jiang, please check in
case I missed anything).
Thanks.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Jiang Liu <liuj97@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sandeepa Prabhu <sandeepa.prabhu@linaro.org>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 6/7] arm64, jump label: optimize jump label implementation
Date: Wed, 8 Jan 2014 15:41:36 +0000 [thread overview]
Message-ID: <20140108154136.GD15212@arm.com> (raw)
In-Reply-To: <20140108110831.GA20644@mudshark.cambridge.arm.com>
On Wed, Jan 08, 2014 at 11:08:32AM +0000, Will Deacon wrote:
> On Wed, Jan 08, 2014 at 11:06:26AM +0000, Jiang Liu wrote:
> > Who should I send this patch set for merging?
>
> Catalin and I will pick up it from here and take it via the arm64 tree, so
> you don't need to do anything.
Done. It should appear in linux-next overnight (Jiang, please check in
case I missed anything).
Thanks.
--
Catalin
next prev parent reply other threads:[~2014-01-08 15:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 14:17 [PATCH v8 0/7] Optimize jump label implementation for ARM64 Jiang Liu
2014-01-07 14:17 ` Jiang Liu
2014-01-07 14:17 ` [PATCH v8 1/7] arm64: introduce basic aarch64 instruction decoding helpers Jiang Liu
2014-01-07 14:17 ` Jiang Liu
2014-01-07 14:17 ` [PATCH v8 2/7] arm64: introduce interfaces to hotpatch kernel and module code Jiang Liu
2014-01-07 14:17 ` Jiang Liu
2014-01-07 14:17 ` [PATCH v8 3/7] arm64: move encode_insn_immediate() from module.c to insn.c Jiang Liu
2014-01-07 14:17 ` Jiang Liu
2014-01-07 14:17 ` [PATCH v8 4/7] arm64: introduce aarch64_insn_gen_{nop|branch_imm}() helper functions Jiang Liu
2014-01-07 14:17 ` Jiang Liu
2014-01-07 14:17 ` [PATCH v8 5/7] arm64, jump label: detect %c support for ARM64 Jiang Liu
2014-01-07 14:17 ` Jiang Liu
2014-01-07 14:17 ` [PATCH v8 6/7] arm64, jump label: optimize jump label implementation Jiang Liu
2014-01-07 14:17 ` Jiang Liu
2014-01-07 15:46 ` Will Deacon
2014-01-07 15:46 ` Will Deacon
2014-01-08 11:06 ` Jiang Liu
2014-01-08 11:06 ` Jiang Liu
2014-01-08 11:08 ` Will Deacon
2014-01-08 11:08 ` Will Deacon
2014-01-08 15:41 ` Catalin Marinas [this message]
2014-01-08 15:41 ` Catalin Marinas
2014-01-07 14:17 ` [PATCH v8 7/7] jump_label: use defined macros instead of hard-coding for better readability Jiang Liu
2014-01-07 14:17 ` Jiang Liu
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=20140108154136.GD15212@arm.com \
--to=catalin.marinas@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.