From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "users@linux.kernel.org" <users@linux.kernel.org>,
tools@linux.kernel.org
Subject: Re: b4 not finding explicitly specified patch
Date: Thu, 20 May 2021 18:06:05 -0400 [thread overview]
Message-ID: <20210520220605.6cnct2wdmjxlz52c@nitro.local> (raw)
In-Reply-To: <CAMuHMdV7gLtcuW6sCJh3HyWpgwr1rcCEEaDkN2L+chZgVMQTpw@mail.gmail.com>
On Thu, Jan 21, 2021 at 11:05:51AM +0100, Geert Uytterhoeven wrote:
> Hi Konstantin,
>
> $ b4 am 20210121082248.883253-1-saravanak@google.com -P_
> Looking up https://lore.kernel.org/r/20210121082248.883253-1-saravanak%40google.com
> Grabbing thread from lore.kernel.org/lkml
> Analyzing 63 messages in the thread
> ---
> Specified msgid is not present in the series, cannot cherrypick
> $
>
> Without "-P_", it downloads a series not containing the patch I want.
Well, only 5 months later, but I do have a fix for this in the current
0.7-dev:
$ b4 am -o/tmp 20210121082248.883253-1-saravanak@google.com -P_
Looking up https://lore.kernel.org/r/20210121082248.883253-1-saravanak%40google.com
Analyzing 5 messages in the thread
Checking attestation on all messages, may take a moment...
---
✓ [PATCH v1] driver: core: Make fw_devlink=on more forgiving
---
✓ Signed: DKIM/google.com
---
Total patches: 1 (cherrypicked: <20210121082248.883253-1-saravanak@google.com>)
---
Link: https://lore.kernel.org/r/20210121082248.883253-1-saravanak@google.com
Base: not found
git am /tmp/20210121_saravanak_driver_core_make_fw_devlink_on_more_forgiving.mbx
Best regards,
-K
next prev parent reply other threads:[~2021-05-20 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 10:05 b4 not finding explicitly specified patch Geert Uytterhoeven
2021-05-20 22:06 ` Konstantin Ryabitsev [this message]
2021-05-21 7:06 ` Geert Uytterhoeven
2021-05-21 12:28 ` Konstantin Ryabitsev
2021-05-21 13:18 ` Geert Uytterhoeven
2021-06-07 7:30 ` Geert Uytterhoeven
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=20210520220605.6cnct2wdmjxlz52c@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=geert@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).