All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Greg KH" <greg@kroah.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: b4 crash on staging driver patchset
Date: Tue, 27 Oct 2020 13:23:15 +0100	[thread overview]
Message-ID: <20201027122315.GA669512@kroah.com> (raw)

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
Looking up https://lore.kernel.org/r/20201019160604.1609180-1-Jerome.Pouiller%40silabs.com
Grabbing thread from lore.kernel.org/driverdev-devel
Analyzing 3 messages in the thread
---
Writing ./20201019_jerome_pouiller_staging_wfx_fix_use_of_uninitialized_pointer.mbx
Traceback (most recent call last):
  File "/mnt/fast_disk/linux/tools/b4/b4/command.py", line 238, in <module>
    cmd()
  File "/mnt/fast_disk/linux/tools/b4/b4/command.py", line 221, in cmd
    cmdargs.func(cmdargs)
  File "/mnt/fast_disk/linux/tools/b4/b4/command.py", line 40, in cmd_am
    b4.mbox.main(cmdargs)
  File "/mnt/fast_disk/linux/tools/b4/b4/mbox.py", line 509, in main
    mbox_to_am(threadmbox, cmdargs)
  File "/mnt/fast_disk/linux/tools/b4/b4/mbox.py", line 114, in mbox_to_am
    am_mbx = lser.save_am_mbox(mbx, noaddtrailers=cmdargs.noaddtrailers,
  File "/mnt/fast_disk/linux/tools/b4/b4/__init__.py", line 522, in save_am_mbox
    latt.validate(lmsg.msg)
AttributeError: 'NoneType' object has no attribute 'validate'

Any hints?

thanks,

greg k-h

             reply	other threads:[~2020-10-27 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 12:23 Greg KH [this message]
2020-10-27 12:51 ` [tools] b4 crash on staging driver patchset Konstantin Ryabitsev
2020-10-27 13:05   ` Greg KH

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=20201027122315.GA669512@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.