Linux Input/HID development
 help / color / mirror / Atom feed
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-kernel@vger.kernel.org,
	 linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 0/2] HID: bpf: fix HID-BPF CI due to new compiler flags
Date: Wed, 07 Jan 2026 15:05:58 +0100	[thread overview]
Message-ID: <176779475850.3423301.194230291511293758.b4-ty@kernel.org> (raw)
In-Reply-To: <20260106-wip-fix-bpf-compilation-v1-0-0b29c85f1157@kernel.org>

On Tue, 06 Jan 2026 16:30:53 +0100, Benjamin Tissoires wrote:
> Since the merge with v6.19-rc my CI is broken because of the newly
> enabled -fms-extensions.
> 
> Add the missing flags when generating the CFLAGS for bpf.o to solve this
> and continue running the tests while applying the patches.
> 
> Cheers,
> Benjamin
> 
> [...]

Applied to hid/hid.git (for-6.19/upstream-fixes), thanks!

[1/2] HID: bpf: fix bpf compilation with -fms-extensions
      https://git.kernel.org/hid/hid/c/b7666c891cc7
[2/2] selftests/hid: fix bpf compilations due to -fms-extensions
      https://git.kernel.org/hid/hid/c/e03fb369b083

Cheers,
-- 
Benjamin Tissoires <bentiss@kernel.org>


      parent reply	other threads:[~2026-01-07 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 15:30 [PATCH 0/2] HID: bpf: fix HID-BPF CI due to new compiler flags Benjamin Tissoires
2026-01-06 15:30 ` [PATCH 1/2] HID: bpf: fix bpf compilation with -fms-extensions Benjamin Tissoires
2026-01-06 15:30 ` [PATCH 2/2] selftests/hid: fix bpf compilations due to -fms-extensions Benjamin Tissoires
2026-01-07 14:05 ` 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=176779475850.3423301.194230291511293758.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=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