From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
"Signed-off-by: Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: b4 commit in -next breaks b4 on next
Date: Wed, 25 Sep 2024 17:31:14 +0100 [thread overview]
Message-ID: <e4a03e2b-63e1-4247-a57e-10bcb75cf7ac@linaro.org> (raw)
Hey.
On commit 2b7275670032a98cba266bd1b8905f755b3e650f (HEAD ->
b4/master-24-11-25-ov08x40, tag: next-20240925, linux-next/master)
exists
commit 3a904d2c771115154380caaae7ffaaf0095fb88f
Author: Benjamin Tissoires <bentiss@kernel.org>
Date: Fri Jul 5 14:07:06 2024 +0200
HID: fix for amples in for-6.11/bpf
To: Jiri Kosina <jikos@kernel.org>
Cc: linux-input@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Benjamin Tissoires <bentiss@kernel.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@kernel.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
next reply other threads:[~2024-09-25 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 16:31 Bryan O'Donoghue [this message]
2024-09-25 20:11 ` b4 commit in -next breaks b4 on next Konstantin Ryabitsev
2024-09-26 8:43 ` Bryan O'Donoghue
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=e4a03e2b-63e1-4247-a57e-10bcb75cf7ac@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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