linux-kernel - Re: linux-next: manual merge of the kvm tree with the drm-xe tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2e1ea7ec-13bd-4582-9052-5de8cb79401d@redhat.com>
Date: Fri, 1 Mar 2024 19:38:40 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Lucas De Marchi <lucas.demarchi@...el.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Oded Gabbay
 <ogabbay@...nel.org>, Thomas Hellström
 <thomas.hellstrom@...ux.intel.com>,
 DRM XE List <intel-xe@...ts.freedesktop.org>, KVM <kvm@...r.kernel.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>,
 Yury Norov <yury.norov@...il.com>
Subject: Re: linux-next: manual merge of the kvm tree with the drm-xe tree

On 3/1/24 19:17, Lucas De Marchi wrote:
> I'm surprised to see 3c7a8e190bc5 ("uapi: introduce uapi-friendly macros
> for GENMASK") with no acks from maintainer though.

The patch sat on the list for a couple months, then I went ahead and 
committed it.

The changes to include/linux/bits.h are just code movement from kernel 
to uapi header (plus the uglification of BITS_PER_LONG and 
BITS_PER_LONG_LONG per uapi rules) so I think that's fine.

But I'll drop an email to them to ask them if they want MAINTAINERS to 
include the new file.

> Btw, aren't you missing some includes in include/uapi/linux/bits.h?

Yeah, uapi/linux/const.h is needed to use the macros in bits.h.  I 
didn't notice because KVM headers include it anyway and, on the 
include/linux/ side, include/linux/bits.h gets it via include/linux/const.h.

Paolo