Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: Acked-by missed when applying
Date: Tue, 5 Oct 2021 13:48:04 +0100	[thread overview]
Message-ID: <YVxJhOU239wRw+no@google.com> (raw)
In-Reply-To: <CAL_JsqKdfMBfrFgu6bmj1HLhwwNFAErj-_dMSizX+dZ0h_B47g@mail.gmail.com>

On Tue, 05 Oct 2021, Rob Herring wrote:

> On Tue, Oct 5, 2021 at 3:02 AM Lee Jones <lee.jones@linaro.org> wrote:
> >
> > Good morning Konstantin,
> >
> > Can you think of a reason why `b4` missed Greg's Ack here?
> 
> Because you applied the first v2 patch, not the second v2 threaded to
> the 1st one that Greg acked.

Not sure I understand.

This is the thread of the patch I merged:

https://i.imgur.com/k4hD9kO.png

Greg's Ack is located in the 5th message down.

> > https://lore.kernel.org/all/YVLA14jbwqXjNM2f@kroah.com/
> >
> > ```
> > + b4 am -3 -slt -P_ -o -
> > '<1828cb783b1ebca0b98bf0b3077d8701adb228f7.1630586862.git.mchehab+huawei@kernel.org>'
> > + git am
> > Looking up https://lore.kernel.org/r/1828cb783b1ebca0b98bf0b3077d8701adb228f7.1630586862.git.mchehab%2Bhuawei%40kernel.org
> > Analyzing 2 messages in the thread
> > Checking attestation on all messages, may take a moment...
> > ---
> >   ✓ [PATCH v2] mfd: hi6421-spmi-pmic: cleanup drvdata
> >     + Signed-off-by: Lee Jones <lee.jones@linaro.org>
> >     + Link: https://lore.kernel.org/r/1828cb783b1ebca0b98bf0b3077d8701adb228f7.1630586862.git.mchehab+huawei@kernel.org
> >   ---
> >   ✓ Signed: DKIM/kernel.org
> > ---
> > Total patches: 1 (cherrypicked:
> > <1828cb783b1ebca0b98bf0b3077d8701adb228f7.1630586862.git.mchehab+huawei@kernel.org>)
> > Prepared a fake commit range for 3-way merge (a0fd2a641207..b603f718647d)
> > ---
> >  Link: https://lore.kernel.org/r/1828cb783b1ebca0b98bf0b3077d8701adb228f7.1630586862.git.mchehab+huawei@kernel.org
> >  Base: applies clean to current tree
> > ```
> >
> > Thanks.
> >
> >

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2021-10-05 12:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05  8:01 Acked-by missed when applying Lee Jones
2021-10-05 12:22 ` Rob Herring
2021-10-05 12:45   ` Konstantin Ryabitsev
2021-10-05 12:49     ` Mark Brown
2021-10-05 13:25       ` Theodore Ts'o
2021-10-05 13:22     ` Lee Jones
2021-10-05 12:48   ` Lee Jones [this message]
2021-10-05 12:53     ` Konstantin Ryabitsev
2021-10-05 13:12       ` Lee Jones
2021-10-05 13:37       ` Mauro Carvalho Chehab
2021-10-05 13:50         ` Lee Jones

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=YVxJhOU239wRw+no@google.com \
    --to=lee.jones@linaro.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=robh@kernel.org \
    --cc=tools@linux.kernel.org \
    --cc=users@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