[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v7 2/3] linux-headers: Update to Linux 6.13-rc7
From: |
Cornelia Huck |
Subject: |
Re: [PATCH v7 2/3] linux-headers: Update to Linux 6.13-rc7 |
Date: |
Thu, 16 Jan 2025 16:57:23 +0100 |
User-agent: |
Notmuch/0.38.3 (https://notmuchmail.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.
[PATCH v7 1/3] linux-headers: Add vmclock-abi.h, David Woodhouse, 2025/01/16
Re: [PATCH v7 0/3] hw/acpi: Add vmclock device, Michael S. Tsirkin, 2025/01/16