Github messages for voidlinux
 help / color / mirror / Atom feed
From: moabeat-berlin <moabeat-berlin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cross-built kernel/dkms improvements
Date: Sun, 01 Oct 2023 12:03:20 +0200	[thread overview]
Message-ID: <20231001100320.QDwVK728whyVj8aDyUTy675tzJW2rr8OdohfvNGX50s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46332@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

New comment by moabeat-berlin on void-packages repository

https://github.com/void-linux/void-packages/pull/46332#issuecomment-1742028581

Comment:
> > * `include/kvm/*` is missing.
> 
> I don't think that's needed, from my testing. what needed it?

The difference is, I added asm-offsets.**c** but the new version of package includes asm-offsets.**s**. The .s file was not part of the original linux kernel tarball, I was using as a reference and is a generated file. Regeneration obviously requires the kvm-headers.

  parent reply	other threads:[~2023-10-01 10:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 21:59 [PR PATCH] " classabbyamp
2023-09-30  1:14 ` [PR PATCH] [Updated] " classabbyamp
2023-09-30 16:46 ` Calandracas606
2023-09-30 16:49 ` Calandracas606
2023-09-30 16:54 ` classabbyamp
2023-09-30 16:54 ` classabbyamp
2023-09-30 17:05 ` Calandracas606
2023-09-30 18:21 ` moabeat-berlin
2023-09-30 22:30 ` moabeat-berlin
2023-10-01  1:06 ` classabbyamp
2023-10-01  1:06 ` classabbyamp
2023-10-01  1:59 ` [PR PATCH] [Updated] " classabbyamp
2023-10-01  3:09 ` Calandracas606
2023-10-01  4:40 ` [PR PATCH] [Updated] " classabbyamp
2023-10-01 10:02 ` moabeat-berlin
2023-10-01 10:03 ` moabeat-berlin [this message]
2023-10-01 15:42 ` Calandracas606
2023-10-01 20:15 ` moabeat-berlin
2023-10-01 20:21 ` [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=20231001100320.QDwVK728whyVj8aDyUTy675tzJW2rr8OdohfvNGX50s@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).