[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJF2gTS0FDgV3toa9wZxPhK2G+f4vCtrru7q3R4FXnMkxYmu-w@mail.gmail.com>
Date: Mon, 21 Nov 2022 19:09:45 +0800
From: Guo Ren <guoren@...nel.org>
To: Conor Dooley <conor.dooley@...rochip.com>
Cc: palmer@...belt.com, paul.walmsley@...ive.com,
aou@...s.berkeley.edu, mhiramat@...nel.org, changbin.du@...el.com,
zong.li@...ive.com, rostedt@...dmis.org, boqun.feng@...il.com,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
Changbin Du <changbin.du@...il.com>
Subject: Re: [PATCH V2] riscv: patch: Fixup lockdep warning in stop_machine
On Mon, Nov 21, 2022 at 6:13 PM Conor Dooley <conor.dooley@...rochip.com> wrote:
>
> On Sun, Nov 20, 2022 at 05:10:49AM -0500, guoren@...nel.org wrote:
> > From: Changbin Du <changbin.du@...il.com>
>
> > Fixes: 0ff7c3b33127 ("riscv: Use text_mutex instead of patch_lock")
> > Cc: Changbin Du <changbin.du@...il.com>
> > Co-developed-by: Guo Ren <guoren@...nel.org>
> > Signed-off-by: Guo Ren <guoren@...nel.org>
> > Cc: Zong Li <zong.li@...ive.com>
> > Cc: Palmer Dabbelt <palmer@...belt.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?
I'm waiting for his SoB. I don't think I could directly use his SoB in
v1. I need him to confirm my rewritten commit log for lockdep
analysis.
>
> 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/
>
--
Best Regards
Guo Ren
Powered by blists - more mailing lists