qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>,
	paul@xen.org, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Ani Sinha <anisinha@redhat.com>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	Eduardo Habkost <eduardo@habkost.net>,
	Peter Hilber <quic_philber@quicinc.com>,
	"Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>
Subject: Re: [PATCH v7 2/3] linux-headers: Update to Linux 6.13-rc7
Date: Thu, 16 Jan 2025 16:57:23 +0100	[thread overview]
Message-ID: <87r05292fw.fsf@redhat.com> (raw)
In-Reply-To: <dcc0b6e46ebbd92ff2b689670731eaa8ffe43b9f.camel@infradead.org>

On Thu, Jan 16 2025, David Woodhouse <dwmw2@infradead.org> wrote:

> On Thu, 2025-01-16 at 15:07 +0100, Paul Durrant wrote:
>> On 16/01/2025 14:59, David Woodhouse wrote:
>> > From: David Woodhouse <dwmw@amazon.co.uk>
>> > 
>> > Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
>> > ---
>> >   include/standard-headers/linux/vmclock-abi.h | 182 +++++++++++++++++++
>> >   linux-headers/linux/iommufd.h                |  31 ++--
>> >   linux-headers/linux/stddef.h                 |  13 +-
>> >   3 files changed, 212 insertions(+), 14 deletions(-)
>> >   create mode 100644 include/standard-headers/linux/vmclock-abi.h
>> > 
>> 
>> No functional change?
>
> Well, other than adding vmclock-abi.h. The rest is almost all in
> comments apart IIRC from the TAG thing, which shouldn't affect us as we
> don't use C++.
>
> I didn't really want to make those other changes but it seems that's
> the process we use; we have to add the new header to the list in
> update-linux-headers.sh and then have a separate commit which runs the
> script again to do a wholesale import.
>
> I suppose I could have cheated and done the import from 6.13-rc1 again,
> but the extra changes did indeed seem like there should be no
> functional change.

If the other headers are not updated by this change, they will be
updated by a later change anyway; IMHO it doesn't really matter when the
headers are updated, as long as the update is done against a specific,
released Linux version. Dragging along other random stuff is normal for
a headers update.



  reply	other threads:[~2025-01-16 15:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 13:59 [PATCH v7 0/3] hw/acpi: Add vmclock device David Woodhouse
2025-01-16 13:59 ` [PATCH v7 1/3] linux-headers: Add vmclock-abi.h David Woodhouse
2025-01-16 15:52   ` Cornelia Huck
2025-01-16 13:59 ` [PATCH v7 2/3] linux-headers: Update to Linux 6.13-rc7 David Woodhouse
2025-01-16 14:07   ` Paul Durrant
2025-01-16 14:10     ` David Woodhouse
2025-01-16 15:57       ` Cornelia Huck [this message]
2025-01-16 13:59 ` [PATCH v7 3/3] hw/acpi: Add vmclock device David Woodhouse
2025-01-16 15:15   ` Philippe Mathieu-Daudé
2025-01-16 15:32     ` David Woodhouse
2025-01-16 15:57       ` Philippe Mathieu-Daudé
2025-01-16 16:01         ` David Woodhouse
2025-01-17 10:44         ` David Woodhouse
2025-02-04 13:49   ` Peter Maydell
2025-02-04 14:17     ` David Woodhouse
2025-02-04 14:52       ` Peter Maydell
2025-02-06 15:11         ` David Woodhouse
2025-02-07 14:34           ` [PATCH] hw/acpi: Remove legacy reset handling from vmclock David Woodhouse
2025-03-29  7:27             ` David Woodhouse
2025-03-30  4:52               ` Ani Sinha
2025-04-09  4:23             ` Ani Sinha
2025-04-09  4:35               ` Ani Sinha
2025-02-04 18:17     ` [PATCH v7 3/3] hw/acpi: Add vmclock device Philippe Mathieu-Daudé
2025-02-04 18:19       ` Philippe Mathieu-Daudé
2025-01-16 14:44 ` [PATCH v7 0/3] " Michael S. Tsirkin
2025-01-16 14:54   ` David Woodhouse
2025-01-17  8:26   ` David Woodhouse

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=87r05292fw.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=abuehaze@amazon.com \
    --cc=anisinha@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=eduardo@habkost.net \
    --cc=imammedo@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quic_philber@quicinc.com \
    --cc=richard.henderson@linaro.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).