mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: zhong jiang <zhongjiang@huawei.com>,
	mingo@kernel.org, linux-kernel@vger.kernel.org,
	Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH 0/2] arm64: remove some extra semicolon
Date: Mon, 1 Oct 2018 14:40:17 +0100	[thread overview]
Message-ID: <20181001134017.GF25071@arrakis.emea.arm.com> (raw)
In-Reply-To: <20180903165934.GK6954@arm.com>

On Mon, Sep 03, 2018 at 05:59:35PM +0100, Will Deacon wrote:
> On Thu, Aug 09, 2018 at 10:20:39PM +0800, zhong jiang wrote:
> > There are some extra semicolon in arm64 architecture. Just remove them.
> 
> These are trivial but certainly not urgent, so I guess Catalin can pick
> them up for 4.20.
> 
> Will
> 
> > zhong jiang (2):
> >   arm64/kprobes: remove an extra semicolon in arch_prepare_kprobe
> >   arm64:guest: remove some extra semicolon in kvm_target_cpu

I picked up the first patch. I'll leave the second to Marc in case there
are any conflicts with the kvm tree.

In case it got lost in inbox, here's the second patch.

https://lore.kernel.org/lkml/1533824441-35661-3-git-send-email-zhongjiang@huawei.com/raw

-- 
Catalin

  parent reply	other threads:[~2018-10-01 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-09 14:20 zhong jiang
2018-08-09 14:20 ` [PATCH 1/2] arm64/kprobes: remove an extra semicolon in arch_prepare_kprobe zhong jiang
2018-08-09 14:20 ` [PATCH 2/2] arm64:guest: remove some extra semicolon in kvm_target_cpu zhong jiang
2018-09-03 16:59 ` [PATCH 0/2] arm64: remove some extra semicolon Will Deacon
2018-09-12 14:38   ` zhong jiang
2018-10-01 13:40   ` Catalin Marinas [this message]
2018-10-01 13:59     ` Marc Zyngier

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=20181001134017.GF25071@arrakis.emea.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mingo@kernel.org \
    --cc=will.deacon@arm.com \
    --cc=zhongjiang@huawei.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

all inboxes | Powered by JetHome®