Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: b4 ignoring Reviewed-by: in quoted-printable email
Date: Tue, 1 Nov 2022 16:16:35 +0100	[thread overview]
Message-ID: <CAMuHMdWS-uK63y1D1qGPOvUbrSuhUnAgiCW+RdChP4xKN67OmA@mail.gmail.com> (raw)
In-Reply-To: <20221101151339.rhp6hys6vnxm4skj@nitro.local>

Hi Konstantin,

On Tue, Nov 1, 2022 at 4:13 PM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
> On Tue, Nov 01, 2022 at 08:30:35AM -0400, Konstantin Ryabitsev wrote:
> > It's actually because that message has a subject that doesn't indicate a
> > follow-up (doesn't have a Re:):
> >
> >     Subject: [PATCH v2] clk: renesas: r9a06g032: Repair grave increment error
> >
> > I'll see if we can recognize this situation, but it's definitely an odd
> > corner-case.
>
> There is a fix for this in master.

Thank you, confirmed.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2022-11-01 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  9:14 b4 ignoring Reviewed-by: in quoted-printable email Geert Uytterhoeven
2022-11-01 12:30 ` Konstantin Ryabitsev
2022-11-01 15:13   ` Konstantin Ryabitsev
2022-11-01 15:16     ` Geert Uytterhoeven [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=CAMuHMdWS-uK63y1D1qGPOvUbrSuhUnAgiCW+RdChP4xKN67OmA@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=tools@linux.kernel.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).