[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aCXvknfaKRzvXLxz@gmail.com>
Date: Thu, 15 May 2025 15:43:46 +0200
From: Ingo Molnar <mingo@...nel.org>
To: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Cc: linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>, linux-arch@...r.kernel.org,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Rich Felker <dalias@...c.org>, linux-sh@...r.kernel.org
Subject: Re: [PATCH 14/15] bugs/sh: Concatenate 'cond_str' with '__FILE__' in
__WARN_FLAGS(), to extend WARN_ON/BUG_ON output
* John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de> wrote:
> On Thu, 2025-05-15 at 15:33 +0200, Ingo Molnar wrote:
> > > It's too long and the prefix "bugs/sh:" is very confusing. I usually just
> > > use "sh:" to mark anything that affects arch/sh.
> >
> > Fair enough, I've changed the title to and pushed out the new tree:
> >
> > sh: Concatenate 'cond_str' with '__FILE__' in __WARN_FLAGS(), to extend WARN_ON/BUG_ON output
>
> Thanks! Minor nitpick: I think that comma is wrong and should be removed
> (I'm not a native speaker though ;-)).
Yeah, so both with and without a comma this sentence is proper English
grammar, but a comma before the 'to' adverb slightly emphasizes the
second part of the sentence, which was my intent with this phrasing.
> > > Can I pick this patch for my sh-linux tree?
> >
> > So since it depends on the previous patches, in isolation this would
> > break the build.
> >
> > Can I add your Reviewed-by or Acked-by?
>
> Yes, sure.
>
> Reviewed-by: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Thanks!
Ingo
Powered by blists - more mailing lists