linux-kernel - b4 commit in -next breaks b4 on next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <e4a03e2b-63e1-4247-a57e-10bcb75cf7ac@linaro.org>
Date: Wed, 25 Sep 2024 17:31:14 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Jiri Kosina <jikos@...nel.org>, Benjamin Tissoires <bentiss@...nel.org>,
 "Signed-off-by: Stephen Rothwell" <sfr@...b.auug.org.au>
Cc: lkml <linux-kernel@...r.kernel.org>
Subject: b4 commit in -next breaks b4 on next

Hey.

On commit 2b7275670032a98cba266bd1b8905f755b3e650f (HEAD -> 
b4/master-24-11-25-ov08x40, tag: next-20240925, linux-next/master)

exists

commit 3a904d2c771115154380caaae7ffaaf0095fb88f
Author: Benjamin Tissoires <bentiss@...nel.org>
Date:   Fri Jul 5 14:07:06 2024 +0200

     HID: fix for amples in for-6.11/bpf

     To: Jiri Kosina <jikos@...nel.org>
     Cc: linux-input@...r.kernel.org
     Cc: linux-kernel@...r.kernel.org
     Signed-off-by: Benjamin Tissoires <bentiss@...nel.org>

     ---
     Changes in v2:
     - EDITME: describe what is new in this series revision.
     - EDITME: use bulletpoints and terse descriptions.
     - Link to v1: 
https://lore.kernel.org/r/20240705-for-6-11-bpf-v1-1-1960e3165c9e@kernel.org



     --- b4-submit-tracking ---
     # This section is used internally by b4 prep for tracking purposes.
     {
       "series": {
         "revision": 2,
         "change-id": "20240705-for-6-11-bpf-a349efc08df8",
         "prefixes": [],
         "history": {
           "v1": [
             "20240705-for-6-11-bpf-v1-1-1960e3165c9e@...nel.org"
           ]
         }
       }
     }

Which means if you run "b4 prep --edit-cover" that is used as the base 
for your b4 series.

You can't revert 3a904d2c771115154380caaae7ffaaf0095fb88f so you 
basically can't use -next for b4 at the moment.

---
bod