public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: guoren@kernel.org
Cc: xianting.tian@linux.alibaba.com, palmer@dabbelt.com,
	heiko@sntech.de, conor.dooley@microchip.com,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org, liaochang1@huawei.com,
	mick@ics.forth.gr, jszhang@kernel.org,
	Guo Ren <guoren@linux.alibaba.com>, Arnd Bergmann <arnd@arndb.de>,
	Will Deacon <will@kernel.org>,
	x86@kernel.org
Subject: Re: [PATCH V3 3/3] arch: crash: Remove duplicate declaration in smp.h
Date: Sat, 20 Aug 2022 10:41:10 +0100	[thread overview]
Message-ID: <YwCsNnfGwkTYShGs@arm.com> (raw)
In-Reply-To: <20220819025444.2121315-4-guoren@kernel.org>

On Thu, Aug 18, 2022 at 10:54:44PM -0400, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
> 
> Remove crash_smp_send_stop declarations in arm64, x86 asm/smp.h which
> has been done in include/linux/smp.h.
> 
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Will Deacon <will@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: x86@kernel.org

Acked-by: Catalin Marinas <catalin.marinas@arm.com>

      reply	other threads:[~2022-08-20  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19  2:54 [PATCH V3 0/3] riscv: kexec: Fixup crash_save percpu and machine_kexec_mask_interrupts guoren
2022-08-19  2:54 ` [PATCH V3 1/3] riscv: kexec: Disable all interrupts in kexec crash path guoren
2022-08-19  2:54 ` [PATCH V3 2/3] riscv: kexec: Fixup crash_smp_send_stop with percpu crash_save_cpu guoren
2022-08-19  2:54 ` [PATCH V3 3/3] arch: crash: Remove duplicate declaration in smp.h guoren
2022-08-20  9:41   ` Catalin Marinas [this message]

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=YwCsNnfGwkTYShGs@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=arnd@arndb.de \
    --cc=conor.dooley@microchip.com \
    --cc=guoren@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=heiko@sntech.de \
    --cc=jszhang@kernel.org \
    --cc=liaochang1@huawei.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mick@ics.forth.gr \
    --cc=palmer@dabbelt.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=xianting.tian@linux.alibaba.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