From: Paolo Bonzini <pbonzini@redhat.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"DRM XE List" <intel-xe@lists.freedesktop.org>,
KVM <kvm@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Yury Norov" <yury.norov@gmail.com>
Subject: Re: linux-next: manual merge of the kvm tree with the drm-xe tree
Date: Fri, 1 Mar 2024 19:38:40 +0100 [thread overview]
Message-ID: <2e1ea7ec-13bd-4582-9052-5de8cb79401d@redhat.com> (raw)
In-Reply-To: <55pdgbv7ltrwnewhxz7ivugowczzomlm6yvco2nxfanxm4ffco@olkrf4wr65so>
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
prev parent reply other threads:[~2024-03-01 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 3:58 linux-next: manual merge of the kvm tree with the drm-xe tree Stephen Rothwell
2024-02-22 10:42 ` Paolo Bonzini
2024-03-01 18:17 ` Lucas De Marchi
2024-03-01 18:38 ` Paolo Bonzini [this message]
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=2e1ea7ec-13bd-4582-9052-5de8cb79401d@redhat.com \
--to=pbonzini@redhat.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=ogabbay@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=thomas.hellstrom@linux.intel.com \
--cc=yury.norov@gmail.com \
/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).