From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/action-ci] 92ec40: ci: add CheckKernelLLVM
Date: Mon, 15 Jun 2026 14:46:20 -0700 [thread overview]
Message-ID: <bluez/action-ci/push/refs/heads/main/979e81-058d4c@github.com> (raw)
Branch: refs/heads/main
Home: https://github.com/bluez/action-ci
Commit: 92ec4064e91267f1d90ae7d9a391100c04ad09d2
https://github.com/bluez/action-ci/commit/92ec4064e91267f1d90ae7d9a391100c04ad09d2
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-06-15 (Mon, 15 Jun 2026)
Changed paths:
M ci.py
M ci/__init__.py
M ci/checkallwarning.py
A ci/checkkernelllvm.py
M ci/generickernelbuild.py
M entrypoint.sh
Log Message:
-----------
ci: add CheckKernelLLVM
Add task to build kernel with LLVM + checking context analysis warnings:
https://docs.kernel.org/dev-tools/context-analysis.html
This feature does static compile time checking of the __must_hold,
__guarded_by etc annotations now used by kernel.
Commit: a562057313abc7aef89ec87faaab11caa5aaf94e
https://github.com/bluez/action-ci/commit/a562057313abc7aef89ec87faaab11caa5aaf94e
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-06-15 (Mon, 15 Jun 2026)
Changed paths:
M entrypoint.sh
M libs/context.py
Log Message:
-----------
entrypoint: add localci command for local CI dry run
Add localci command so that the docker CI can be tested locally without
secrets.
Example:
git clone --depth 1 https://github.com/bluez/bluetooth-next work/src
docker run --volume $PWD/work:/work/base:O $IMG localci kernel bluez/bluetooth-next 103
Commit: 058d4cc766443e37c4c1150f44d474b4e98dc61e
https://github.com/bluez/action-ci/commit/058d4cc766443e37c4c1150f44d474b4e98dc61e
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-06-15 (Mon, 15 Jun 2026)
Changed paths:
M ci.py
M ci/buildbluez.py
M ci/buildell.py
M ci/buildkernel.py
M ci/buildkernel32.py
M ci/checkallwarning.py
M ci/checksparse.py
M ci/checkvalgrind.py
M ci/genericbuild.py
M ci/generickernelbuild.py
M ci/incrementalbuild.py
M ci/makedistcheck.py
M ci/makeextell.py
M ci/scanbuild.py
M entrypoint.sh
Log Message:
-----------
ci: add --jobs setting to set make -j
Add option for setting make -j option value.
Compare: https://github.com/bluez/action-ci/compare/979e8164c387...058d4cc76644
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/action-ci/settings/notifications
reply other threads:[~2026-06-15 21:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/action-ci/push/refs/heads/main/979e81-058d4c@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.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