public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
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

  reply	other threads:[~2014-01-08 15:41 UTC|newest]

Thread overview: 12+ 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 ` [PATCH v8 1/7] arm64: introduce basic aarch64 instruction decoding helpers 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 ` [PATCH v8 3/7] arm64: move encode_insn_immediate() from module.c to insn.c 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 ` [PATCH v8 5/7] arm64, jump label: detect %c support for ARM64 Jiang Liu
2014-01-07 14:17 ` [PATCH v8 6/7] arm64, jump label: optimize jump label implementation Jiang Liu
2014-01-07 15:46   ` Will Deacon
2014-01-08 11:06     ` Jiang Liu
2014-01-08 11:08       ` Will Deacon
2014-01-08 15:41         ` Catalin Marinas [this message]
2014-01-07 14:17 ` [PATCH v8 7/7] jump_label: use defined macros instead of hard-coding for better readability 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$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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