qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: David Turner <digit@google.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 2/2] Add missing Linux kernel headers.
Date: Wed, 05 Apr 2023 17:54:16 +0200	[thread overview]
Message-ID: <87mt3mxr2v.fsf@redhat.com> (raw)
In-Reply-To: <CACnJMqrf-YH6P0zBC4FSSp_LcO=pxDOrx-P3MGGFDj_uWbWjvg@mail.gmail.com>

On Wed, Apr 05 2023, David Turner <digit@google.com> wrote:

> On Wed, Apr 5, 2023 at 3:06 PM Cornelia Huck <cohuck@redhat.com> wrote:
>
>> On Wed, Apr 05 2023, "David 'Digit' Turner" <digit@google.com> wrote:
>> > The script has then been run against the official
>> > 6.2.8 kernel source tree (current stable release),
>> > which explains why comments in <linux/vfio.h>
>> > have been updated too.
>>
>> I think we usually run the script against a release or release
>> candidate, not stable.
>>
>> I meant that this was run against the headers of the 6.2.8 official
> release, which was listed as "stable" on https://kernel.org/ (that page now
> lists the 6.2.9 release btw)
> I'd be happy to re-run it against a different set if you can tell me which
> one (and where to get it, just in case).

I think most people actually run it against a checkout of Linus' git
tree, preferrably either the latest -rc version (or the latest release
during the kernel merge window) -- people usually run the script because
they want to use some new interfaces that were recently introduced to
the kernel. (This also ensures linear history, although I don't think
that's too much of a problem.)

Just make sure you note the exact version (or git hash), then it's
fine. Might also be worth splitting this into adding the new files to
the script and actually updating the headers.



  reply	other threads:[~2023-04-05 15:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 12:59 [PATCH 0/2] Fix QEMU compilation on Debian 10 David 'Digit' Turner
2023-04-05 12:59 ` [PATCH 1/2] Fix libvhost-user.c compilation David 'Digit' Turner
2023-04-07  7:56   ` Michael S. Tsirkin
2023-04-26 19:13     ` Paolo Bonzini
2023-04-05 12:59 ` [PATCH 2/2] Add missing Linux kernel headers David 'Digit' Turner
2023-04-05 13:06   ` Cornelia Huck
2023-04-05 13:42     ` David Turner
2023-04-05 15:54       ` Cornelia Huck [this message]
2023-04-05 16:41         ` Peter Maydell
2023-04-05 17:22           ` David Turner
2023-04-26 19:10 ` [PATCH 0/2] Fix QEMU compilation on Debian 10 Paolo Bonzini

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=87mt3mxr2v.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=digit@google.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).