b4 commit in -next breaks b4 on next

[Bryan O'Donoghue]

Hey.

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

exists

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

    HID: fix for amples in for-6.11/bpf

    To: Jiri Kosina <jikos@xxxxxxxxxx>
    Cc: linux-input@xxxxxxxxxxxxxxx
    Cc: linux-kernel@xxxxxxxxxxxxxxx
    Signed-off-by: Benjamin Tissoires <bentiss@xxxxxxxxxx>

    ---
    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@xxxxxxxxxx



    --- 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@xxxxxxxxxx"
          ]
        }
      }
    }

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