All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: <guoren@kernel.org>
Cc: <palmer@dabbelt.com>, <paul.walmsley@sifive.com>,
	<aou@eecs.berkeley.edu>, <mhiramat@kernel.org>,
	<changbin.du@intel.com>, <zong.li@sifive.com>,
	<rostedt@goodmis.org>, <boqun.feng@gmail.com>,
	<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
	Changbin Du <changbin.du@gmail.com>
Subject: Re: [PATCH V2] riscv: patch: Fixup lockdep warning in stop_machine
Date: Mon, 21 Nov 2022 10:12:32 +0000	[thread overview]
Message-ID: <Y3tPEDvM3aVJmVxF@wendy> (raw)
In-Reply-To: <20221120101049.2078117-1-guoren@kernel.org>

On Sun, Nov 20, 2022 at 05:10:49AM -0500, guoren@kernel.org wrote:
> From: Changbin Du <changbin.du@gmail.com>

> Fixes: 0ff7c3b33127 ("riscv: Use text_mutex instead of patch_lock")
> Cc: Changbin Du <changbin.du@gmail.com>
> Co-developed-by: Guo Ren <guoren@kernel.org>
> Signed-off-by: Guo Ren <guoren@kernel.org>
> Cc: Zong Li <zong.li@sifive.com>
> Cc: Palmer Dabbelt <palmer@dabbelt.com>
> ---

Hey Guo Ren,

FYI you're missing a SoB from Chanbin on this patch. They gave one in
their v1 though so you should be able to re-use that?

Thanks,
Conor.

> Changes in v2:
>  - Rewrite commit log with lockdep explanation [Guo Ren]
>  - Rebase on v6.1 [Guo Ren]
> 
> v1:
> https://lore.kernel.org/linux-riscv/20210417023532.354714-1-changbin.du@gmail.com/


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

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
To: <guoren@kernel.org>
Cc: <palmer@dabbelt.com>, <paul.walmsley@sifive.com>,
	<aou@eecs.berkeley.edu>, <mhiramat@kernel.org>,
	<changbin.du@intel.com>, <zong.li@sifive.com>,
	<rostedt@goodmis.org>, <boqun.feng@gmail.com>,
	<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
	Changbin Du <changbin.du@gmail.com>
Subject: Re: [PATCH V2] riscv: patch: Fixup lockdep warning in stop_machine
Date: Mon, 21 Nov 2022 10:12:32 +0000	[thread overview]
Message-ID: <Y3tPEDvM3aVJmVxF@wendy> (raw)
In-Reply-To: <20221120101049.2078117-1-guoren@kernel.org>

On Sun, Nov 20, 2022 at 05:10:49AM -0500, guoren@kernel.org wrote:
> From: Changbin Du <changbin.du@gmail.com>

> Fixes: 0ff7c3b33127 ("riscv: Use text_mutex instead of patch_lock")
> Cc: Changbin Du <changbin.du@gmail.com>
> Co-developed-by: Guo Ren <guoren@kernel.org>
> Signed-off-by: Guo Ren <guoren@kernel.org>
> Cc: Zong Li <zong.li@sifive.com>
> Cc: Palmer Dabbelt <palmer@dabbelt.com>
> ---

Hey Guo Ren,

FYI you're missing a SoB from Chanbin on this patch. They gave one in
their v1 though so you should be able to re-use that?

Thanks,
Conor.

> Changes in v2:
>  - Rewrite commit log with lockdep explanation [Guo Ren]
>  - Rebase on v6.1 [Guo Ren]
> 
> v1:
> https://lore.kernel.org/linux-riscv/20210417023532.354714-1-changbin.du@gmail.com/


  reply	other threads:[~2022-11-21 10:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 10:10 [PATCH V2] riscv: patch: Fixup lockdep warning in stop_machine guoren
2022-11-20 10:10 ` guoren
2022-11-21 10:12 ` Conor Dooley [this message]
2022-11-21 10:12   ` Conor Dooley
2022-11-21 11:09   ` Guo Ren
2022-11-21 11:09     ` Guo Ren
2022-12-22  0:19     ` Changbin Du
2022-12-22  0:19       ` Changbin Du
2022-12-22  0:29       ` Conor Dooley
2022-12-22  0:29         ` Conor Dooley
2022-12-22 12:23         ` Changbin Du
2022-12-22 12:23           ` Changbin Du
2022-12-22  2:43       ` Guo Ren
2022-12-22  2:43         ` Guo Ren
2022-12-22 12:22 ` Changbin Du
2022-12-22 12:22   ` Changbin Du

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=Y3tPEDvM3aVJmVxF@wendy \
    --to=conor.dooley@microchip.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=boqun.feng@gmail.com \
    --cc=changbin.du@gmail.com \
    --cc=changbin.du@intel.com \
    --cc=guoren@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mhiramat@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rostedt@goodmis.org \
    --cc=zong.li@sifive.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 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.