From: "Greg KH" <greg@kroah.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: [tools] b4 crash on staging driver patchset
Date: Tue, 27 Oct 2020 14:05:07 +0100 [thread overview]
Message-ID: <20201027130507.GA745673@kroah.com> (raw)
In-Reply-To: <20201027125155.u7ttdwpdsz722rkw@chatter.i7.local>
On Tue, Oct 27, 2020 at 08:51:55AM -0400, Konstantin Ryabitsev wrote:
> On Tue, Oct 27, 2020 at 01:23:15PM +0100, Greg KH wrote:
> > Hi Konstantin,
> >
> > On the latest tip of the 'b4' tree, I get the following crash with this
> > patch series:
> >
> > $ b4 am -t https://lore.kernel.org/r/20201019160604.1609180-1-Jerome.Pouiller@silabs.com
>
> Ah, good find -- we need to fix the horrible base64 encoding legacy crud
> before we try to attest a message. There's a fix for it in the latest
> master.
Thanks for the quick fix, works for me!
greg k-h
prev parent reply other threads:[~2020-10-27 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 12:23 b4 crash on staging driver patchset Greg KH
2020-10-27 12:51 ` [tools] " Konstantin Ryabitsev
2020-10-27 13:05 ` Greg KH [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=20201027130507.GA745673@kroah.com \
--to=greg@kroah.com \
--cc=konstantin@linuxfoundation.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).