From: Benjamin Tissoires <bentiss@kernel.org>
To: Jiri Kosina <jikos@kernel.org>, Shuah Khan <shuah@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Mirsad Todorovac <mtodorovac69@gmail.com>
Subject: Re: [PATCH v2 0/4] Fix warnings in for-6.11/bpf
Date: Mon, 01 Jul 2024 15:46:38 +0200 [thread overview]
Message-ID: <171984159899.804118.13748285528625314885.b4-ty@kernel.org> (raw)
In-Reply-To: <20240701-fix-cki-v2-0-20564e2e1393@kernel.org>
On Mon, 01 Jul 2024 14:39:48 +0200, Benjamin Tissoires wrote:
> We had several complains in linux-next that there were warnings:
>
> CKI was not happy: it was the same situation than in an early report
> when HID-BPF was initially included: the automatically generated
> vmlinux.h doesn't contain all of the required structs and the
> compilation of the bpf program fails.
>
> [...]
Applied to hid/hid.git (for-6.11/bpf), thanks!
[1/4] selftests/hid: ensure CKI can compile our new tests on old kernels
https://git.kernel.org/hid/hid/c/fcdf830ea634
[2/4] HID: bpf: fix gcc warning and unify __u64 into u64
https://git.kernel.org/hid/hid/c/762ced1630a9
[3/4] HID: bpf: doc fixes for hid_hw_request() hooks
https://git.kernel.org/hid/hid/c/c79de517a226
[4/4] HID: bpf: doc fixes for hid_hw_request() hooks
https://git.kernel.org/hid/hid/c/c79de517a226
Cheers,
--
Benjamin Tissoires <bentiss@kernel.org>
prev parent reply other threads:[~2024-07-01 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 12:39 Benjamin Tissoires
2024-07-01 12:39 ` [PATCH v2 1/4] selftests/hid: ensure CKI can compile our new tests on old kernels Benjamin Tissoires
2024-07-01 12:39 ` [PATCH v2 2/4] HID: bpf: fix gcc warning and unify __u64 into u64 Benjamin Tissoires
2024-07-01 12:39 ` [PATCH v2 3/4] HID: bpf: doc fixes for hid_hw_request() hooks Benjamin Tissoires
2024-07-01 12:39 ` [PATCH v2 4/4] " Benjamin Tissoires
2024-07-01 13:46 ` Benjamin Tissoires [this message]
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=171984159899.804118.13748285528625314885.b4-ty@kernel.org \
--to=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mtodorovac69@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=shuah@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 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®