All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	tools@linux.kernel.org, users@linux.kernel.org
Subject: b4 patch subject issue
Date: Tue, 15 Nov 2022 21:17:57 +0100	[thread overview]
Message-ID: <Y3Pz9Y9Mn1FtnqR1@mail.local> (raw)

Hello Konstantin,

I found a small issue in how b4 handles path subjects:

linux$ b4 shazam -tsl 5640233.DvuYhMxLoT@kreacher
Grabbing thread from lore.kernel.org/all/5640233.DvuYhMxLoT%40kreacher/t.mbox.gz
Checking for newer revisions on https://lore.kernel.org/all/
Analyzing 9 messages in the thread
Checking attestation on all messages, may take a moment...
---
  [PATCH v2 1/5] rtc: rtc-cmos: Call cmos_wake_setup() from cmos_do_probe()
    + Reviewed-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
    + Tested-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
    + Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> (✓ DKIM/intel.com)
    + Link: https://lore.kernel.org/r/4803444.31r3eYUQgx@kreacher
    + Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
  [PATCH v2 2/5] rtc: rtc-cmos: Call rtc_wake_setup() from cmos_do_probe()
    + Reviewed-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
    + Tested-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
    + Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> (✓ DKIM/intel.com)
    + Link: https://lore.kernel.org/r/2143522.irdbgypaU6@kreacher
    + Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
  [PATCH v2 3/5] rtc: rtc-cmos: Eliminate forward declarations of some functions
    + Reviewed-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
    + Tested-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
    + Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> (✓ DKIM/intel.com)
    + Link: https://lore.kernel.org/r/13157911.uLZWGnKmhe@kreacher
    + Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
  [PATCH v2 4/5] rtc: rtc-cmos: Rename ACPI-related functions
    + Reviewed-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
    + Tested-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
    + Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> (✓ DKIM/intel.com)
    + Link: https://lore.kernel.org/r/3225614.44csPzL39Z@kreacher
    + Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
  [PATCH v2 5/5] rtc: rtc-cmos: Disable ACPI RTC event on removal
    + Reviewed-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
    + Tested-by: Zhang Rui <rui.zhang@intel.com> (✓ DKIM/intel.com)
    + Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> (✓ DKIM/intel.com)
    + Link: https://lore.kernel.org/r/2224609.iZASKD2KPV@kreacher
    + Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
---
Total patches: 5
---
Applying: rtc: rtc-cmos: Call cmos_wake_setup() from cmos_do_probe()
Applying: rtc: rtc-cmos: Call rtc_wake_setup() from cmos_do_probe()
Applying: rtc: rtc-cmos:
Applying: rtc: rtc-cmos: Rename ACPI-related functions
Applying: rtc: rtc-cmos: Disable ACPI RTC event on removal
---
Patchwork: setting state on patchwork.ozlabs.org/rtc-linux
 -> under-review : [v2,1/5] rtc: rtc-cmos: Call cmos_wake_setup() from cmos_do_probe()
 -> under-review : [v2,2/5] rtc: rtc-cmos: Call rtc_wake_setup() from cmos_do_probe()
 -> under-review : [v2,3/5] rtc: rtc-cmos: Eliminate forward declarations of some functions
 -> under-review : [v2,4/5] rtc: rtc-cmos: Rename ACPI-related functions
 -> under-review : [v2,5/5] rtc: rtc-cmos: Disable ACPI RTC event on removal
linux$ git log --oneline -5
dfe59ef27467 (HEAD -> plop) rtc: rtc-cmos: Disable ACPI RTC event on removal
f02e8f979e26 rtc: rtc-cmos: Rename ACPI-related functions
a9f73fde7380 rtc: rtc-cmos:
70258aa62244 rtc: rtc-cmos: Call rtc_wake_setup() from cmos_do_probe()
1c399f3090f7 rtc: rtc-cmos: Call cmos_wake_setup() from cmos_do_probe()

For some reason, 3/5 is losing its full subject. I didn't investigate
but I'm using a freshly updated b4 0.10.1 on fedora.

Let me know if I can be of any assistance to debug that.

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

             reply	other threads:[~2022-11-15 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 20:17 Alexandre Belloni [this message]
2022-11-15 20:28 ` b4 patch subject issue Konstantin Ryabitsev
2022-11-15 20:43   ` Alexandre Belloni

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=Y3Pz9Y9Mn1FtnqR1@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=dmitry.torokhov@gmail.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.