From: Bjorn Helgaas <helgaas@kernel.org>
To: tools@linux.kernel.org
Subject: b4 corrupts patch
Date: Thu, 8 Apr 2021 11:02:26 -0500 [thread overview]
Message-ID: <20210408160226.GA1932146@bjorn-Precision-5520> (raw)
b4 seems to corrupt this patch when fetching and adding a Reviewed-by
tag:
https://lore.kernel.org/r/b411af88-5049-a1c6-83ac-d104a1f429be@huawei.com
It applies fine if I save the message from Mutt or if I wget it by
hand from
https://lore.kernel.org/linux-acpi/b411af88-5049-a1c6-83ac-d104a1f429be@huawei.com/raw
$ b4 --version
0.6.2
$ b4 am -om/ https://lore.kernel.org/r/b411af88-5049-a1c6-83ac-d104a1f429be@huawei.com
Looking up https://lore.kernel.org/r/b411af88-5049-a1c6-83ac-d104a1f429be%40huawei.com
Grabbing thread from lore.kernel.org/linux-acpi
Analyzing 3 messages in the thread
---
Writing m/v2_20210325_liuzhiqiang26_acpi_hotplug_pci_fix_memory_leak_in_enable_slot.mbx
[PATCH v2] ACPI / hotplug / PCI: fix memory leak in enable_slot()
+ Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
Total patches: 1
---
Link: https://lore.kernel.org/r/b411af88-5049-a1c6-83ac-d104a1f429be@huawei.com
Base: not found (applies clean to current tree)
git am m/v2_20210325_liuzhiqiang26_acpi_hotplug_pci_fix_memory_leak_in_enable_slot.mbx
$ git am m/v2_20210325_liuzhiqiang26_acpi_hotplug_pci_fix_memory_leak_in_enable_slot.mbx
Applying: ACPI / hotplug / PCI: fix memory leak in enable_slot()
error: corrupt patch at line 17
Patch failed at 0001 ACPI / hotplug / PCI: fix memory leak in enable_slot()
next reply other threads:[~2021-04-08 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 16:02 Bjorn Helgaas [this message]
2021-04-08 16:18 ` b4 corrupts patch Konstantin Ryabitsev
2021-04-08 17:01 ` Bjorn Helgaas
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=20210408160226.GA1932146@bjorn-Precision-5520 \
--to=helgaas@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 NNTP newsgroup(s).