From: moabeat-berlin <moabeat-berlin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland)
Date: Sun, 24 Sep 2023 02:21:06 +0200 [thread overview]
Message-ID: <20230924002106.v1ZPMBIWHt_xEvxd5Lku3Q6YMpLlst32HJjlB59l8vI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46152@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
New comment by moabeat-berlin on void-packages repository
https://github.com/void-linux/void-packages/pull/46152#issuecomment-1732440086
Comment:
Right, `make prepare0` seems to be sufficient for `/etc/kernel.d/post-install/10-dkms` and also installing a dkms package after the kernel and headers have already been installed before seems to work. Since `vdso_prepare` is only a prerequisite for the `prepare` target, they seem to be not required.
```
grep -r "^prepare:" .
./Makefile:prepare: prepare0
./Makefile:prepare: headers
./Makefile:prepare: tools/objtool
./Makefile:prepare: tools/bpf/resolve_btfids
./Makefile:prepare: CC_VERSION_TEXT := $(CC_VERSION_TEXT)
./Makefile:prepare:
./arch/arm64/Makefile:prepare: stack_protector_prepare
./arch/arm64/Makefile:prepare: vdso_prepare <-- here
./Kbuild:prepare: $(offsets-file) missing-syscalls $(atomic-checks)
```
next prev parent reply other threads:[~2023-09-24 0:21 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 11:34 [PR PATCH] rpi-kernel: update to 6.1.54 classabbyamp
2023-09-20 12:35 ` rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland) r-ricci
2023-09-20 13:36 ` tsjk
2023-09-20 13:37 ` tsjk
2023-09-20 16:41 ` classabbyamp
2023-09-23 19:03 ` moabeat-berlin
2023-09-23 19:12 ` classabbyamp
2023-09-23 19:28 ` moabeat-berlin
2023-09-23 19:29 ` moabeat-berlin
2023-09-23 23:11 ` [PR PATCH] [Updated] " classabbyamp
2023-09-23 23:12 ` classabbyamp
2023-09-23 23:13 ` classabbyamp
2023-09-23 23:15 ` classabbyamp
2023-09-23 23:28 ` moabeat-berlin
2023-09-23 23:29 ` moabeat-berlin
2023-09-23 23:59 ` classabbyamp
2023-09-24 0:20 ` moabeat-berlin
2023-09-24 0:21 ` moabeat-berlin [this message]
2023-09-24 17:53 ` tsjk
2023-09-24 17:54 ` tsjk
2023-09-24 17:54 ` tsjk
2023-09-24 19:53 ` tsjk
2023-09-25 6:33 ` [PR PATCH] [Updated] " classabbyamp
2023-09-25 6:40 ` classabbyamp
2023-09-25 8:44 ` tsjk
2023-09-25 8:45 ` tsjk
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:29 ` classabbyamp
2023-09-29 18:37 ` tsjk
2023-09-29 18:40 ` classabbyamp
2023-09-29 18:41 ` tsjk
2023-09-29 19:01 ` classabbyamp
2023-09-29 19:01 ` classabbyamp
2023-09-29 19:01 ` classabbyamp
2023-09-29 19:05 ` classabbyamp
2023-09-29 19:37 ` [PR PATCH] [Updated] " classabbyamp
2023-09-29 20:57 ` moabeat-berlin
2023-09-29 21:09 ` classabbyamp
2023-09-29 21:18 ` classabbyamp
2023-09-29 21:24 ` [PR PATCH] [Updated] " classabbyamp
2023-09-29 22:01 ` rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland, rpi-eeprom) classabbyamp
2023-09-30 2:41 ` [PR PATCH] [Merged]: " classabbyamp
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=20230924002106.v1ZPMBIWHt_xEvxd5Lku3Q6YMpLlst32HJjlB59l8vI@z \
--to=moabeat-berlin@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).