All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Guo <dongtai.guo@linux.dev>
To: mark.rutland@arm.com
Cc: ardb@kernel.org, catalin.marinas@arm.com, dongtai.guo@linux.dev,
	guodongtai@kylinos.cn, jbaron@akamai.com, jpoimboe@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	rostedt@goodmis.org, will@kernel.org
Subject: [PATCH v3 0/1] cleanup arch_static_branch/_jump
Date: Tue, 30 Apr 2024 16:56:54 +0800	[thread overview]
Message-ID: <20240430085655.2798551-1-dongtai.guo@linux.dev> (raw)
In-Reply-To: <ZiYs3itsmdOmuPq4@FVFF77S0Q05N>

From: George Guo <guodongtai@kylinos.cn>

Hi Mark, 
I have tried to define macro with key and lable in v3.
What do you think on v3 patch?

George Guo (1):
  arm64: simplify arch_static_branch/_jump function

 arch/arm64/include/asm/jump_label.h | 28 +++++++++++++++-------------
 1 file changed, 15 insertions(+), 13 deletions(-)

-- 
2.34.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: George Guo <dongtai.guo@linux.dev>
To: mark.rutland@arm.com
Cc: ardb@kernel.org, catalin.marinas@arm.com, dongtai.guo@linux.dev,
	guodongtai@kylinos.cn, jbaron@akamai.com, jpoimboe@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	rostedt@goodmis.org, will@kernel.org
Subject: [PATCH v3 0/1] cleanup arch_static_branch/_jump
Date: Tue, 30 Apr 2024 16:56:54 +0800	[thread overview]
Message-ID: <20240430085655.2798551-1-dongtai.guo@linux.dev> (raw)
In-Reply-To: <ZiYs3itsmdOmuPq4@FVFF77S0Q05N>

From: George Guo <guodongtai@kylinos.cn>

Hi Mark, 
I have tried to define macro with key and lable in v3.
What do you think on v3 patch?

George Guo (1):
  arm64: simplify arch_static_branch/_jump function

 arch/arm64/include/asm/jump_label.h | 28 +++++++++++++++-------------
 1 file changed, 15 insertions(+), 13 deletions(-)

-- 
2.34.1


  parent reply	other threads:[~2024-04-30  8:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22  6:38 [PATCH 1/1] arm64: optimize code duplication in arch_static_branch/_jump function George Guo
2024-04-22  6:38 ` George Guo
2024-04-22  9:24 ` Mark Rutland
2024-04-22  9:24   ` Mark Rutland
2024-04-25  9:21   ` [PATCH v2 0/1] cleanup arch_static_branch/_jump George Guo
2024-04-25  9:21     ` George Guo
2024-04-25  9:21     ` [PATCH v2 1/1] arm64: simplify arch_static_branch/_jump function George Guo
2024-04-25  9:21       ` George Guo
2024-04-30  8:56   ` George Guo [this message]
2024-04-30  8:56     ` [PATCH v3 0/1] cleanup arch_static_branch/_jump George Guo
2024-04-30  8:56     ` [PATCH v3 1/1] arm64: simplify arch_static_branch/_jump function George Guo
2024-04-30  8:56       ` George Guo
2024-05-03 17:32     ` [PATCH v3 0/1] cleanup arch_static_branch/_jump Will Deacon
2024-05-03 17:32       ` 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=20240430085655.2798551-1-dongtai.guo@linux.dev \
    --to=dongtai.guo@linux.dev \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=guodongtai@kylinos.cn \
    --cc=jbaron@akamai.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=will@kernel.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.