[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220902192950.ojetwk6fkhjzo7xg@meerkat.local>
Date: Fri, 2 Sep 2022 15:29:50 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Conor.Dooley@...rochip.com
Cc: heiko@...ech.de, ajones@...tanamicro.com, paul.walmsley@...ive.com,
palmer@...belt.com, aou@...s.berkeley.edu, guoren@...nel.org,
apatel@...tanamicro.com, atishp@...osinc.com,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] riscv: cleanup svpbmt cpufeature probing
On Fri, Sep 02, 2022 at 03:26:21PM +0000, Conor.Dooley@...rochip.com wrote:
> >> Reviewed-by: Andrew Jones <ajones@...tanamicro.com>
> >>
> >> but now it looks like I need to go back and reply to each patch
> >> separately.
> >
> > I'm not sure if tooling like b4 can handle Reviewed-by's in cover-letters.
>
> Yup, it can! At least `b4 {am,shazam} -t` will.
> I am not sure if the new `b4 trailers` does.
Yes, it's the default behaviour for "b4 trailers". It'll probably become the
default for "b4 am/shazam" at some point, too.
-K
Powered by blists - more mailing lists