From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jiri Kosina <jikos@kernel.org>,
linux-kernel@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [GIT PULL] HID for 6.11
Date: Mon, 22 Jul 2024 15:32:48 +0200 [thread overview]
Message-ID: <3610ec4c-524a-4cd7-93a9-16023618a49d@kernel.org> (raw)
In-Reply-To: <c52b7bf6-734b-49fd-96e3-e4cde406f4e0@linaro.org>
On 22/07/2024 14:46, Konrad Dybcio wrote:
>
>
> On 16.07.2024 3:34 PM, Benjamin Tissoires wrote:
>> Linus,
>>
>> please pull from
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git tags/for-linus-2024071601
>>
>> to receive HID subsystem updates for 6.11 merge window. Highlights:
>>
>
> [...]
>
>> HID: bpf: Add support for the XP-PEN Deco Mini 4
>> HID: bpf: Add Huion Dial 2 bpf fixup
>> HID: bpf: Thrustmaster TCA Yoke Boeing joystick fix
>> HID: fix for amples in for-6.11/bpf
>
> Hi,
>
> this commit broke b4 for everyone starting next-20240719, as it's
> an empty cover letter with b4 tracking information
Konrad gave me idea which could at least protect final tree from such
mistakes - commit hook for merges, something like:
https://github.com/krzk/tools/blob/master/linux/verify_b4.sh
https://github.com/krzk/tools/blob/master/linux/git-hooks-post-merge
(maybe also post-commit in case of conflicts?)
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-22 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 13:34 Benjamin Tissoires
2024-07-18 0:29 ` Linus Torvalds
2024-07-18 1:27 ` pr-tracker-bot
2024-07-22 12:46 ` Konrad Dybcio
2024-07-22 12:51 ` Krzysztof Kozlowski
2024-07-22 12:56 ` Krzysztof Kozlowski
2024-07-22 13:51 ` Benjamin Tissoires
2024-07-22 13:59 ` Benjamin Tissoires
2024-08-06 22:04 ` Jacob Keller
2024-07-22 13:32 ` Krzysztof Kozlowski [this message]
2024-07-22 13:58 ` Konstantin Ryabitsev
2024-07-22 18:17 ` Konstantin Ryabitsev
2024-07-23 11:26 ` Konrad Dybcio
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=3610ec4c-524a-4cd7-93a9-16023618a49d@kernel.org \
--to=krzk@kernel.org \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®