mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex@shazbot.org>
To: David Matlack <dmatlack@google.com>
Cc: Alex Mastro <amastro@fb.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Josh Hilke <jrhilke@google.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Raghavendra Rao Ananta <rananta@google.com>,
	Shuah Khan <shuah@kernel.org>,
	Wei Yang <richard.weiyang@gmail.com>,
	Yosry Ahmed <yosryahmed@google.com>
Subject: Re: [PATCH 0/2] vfio: selftests: Clean up <uapi/linux/types.h> includes
Date: Tue, 23 Dec 2025 16:42:02 -0700	[thread overview]
Message-ID: <20251223164202.34ea5015.alex@shazbot.org> (raw)
In-Reply-To: <20251219233818.1965306-1-dmatlack@google.com>

On Fri, 19 Dec 2025 23:38:16 +0000
David Matlack <dmatlack@google.com> wrote:

> Small clean up series to eliminate the extra includes of
> <uapi/linux/types.h> from various VFIO selftests files. This include is
> not causing any problems now, but it is causing benign typedef
> redifinitions. Those redifinitions will become a problem when the VFIO
> selftests library is built into KVM selftests, since KVM selftests build
> with -std=gnu99.
> 
> Cc: Yosry Ahmed <yosryahmed@google.com>
> Cc: Josh Hilke <jrhilke@google.com>
> 
> David Matlack (2):
>   tools include: Add definitions for __aligned_{l,b}e64
>   vfio: selftests: Drop <uapi/linux/types.h> includes
> 
>  tools/include/linux/types.h                               | 8 ++++++++
>  .../selftests/vfio/lib/include/libvfio/iova_allocator.h   | 1 -
>  tools/testing/selftests/vfio/lib/iommu.c                  | 1 -
>  tools/testing/selftests/vfio/lib/iova_allocator.c         | 1 -
>  tools/testing/selftests/vfio/lib/vfio_pci_device.c        | 1 -
>  tools/testing/selftests/vfio/vfio_dma_mapping_test.c      | 1 -
>  tools/testing/selftests/vfio/vfio_iommufd_setup_test.c    | 1 -
>  7 files changed, 8 insertions(+), 6 deletions(-)
> 
> 
> base-commit: d721f52e31553a848e0e9947ca15a49c5674aef3

Applied to vfio for-linus branch for v6.19.  Thanks,

Alex

      parent reply	other threads:[~2025-12-23 23:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 23:38 David Matlack
2025-12-19 23:38 ` [PATCH 1/2] tools include: Add definitions for __aligned_{l,b}e64 David Matlack
2025-12-19 23:38 ` [PATCH 2/2] vfio: selftests: Drop <uapi/linux/types.h> includes David Matlack
2025-12-23 23:42 ` Alex Williamson [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=20251223164202.34ea5015.alex@shazbot.org \
    --to=alex@shazbot.org \
    --cc=akpm@linux-foundation.org \
    --cc=amastro@fb.com \
    --cc=dmatlack@google.com \
    --cc=jrhilke@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=rananta@google.com \
    --cc=richard.weiyang@gmail.com \
    --cc=shuah@kernel.org \
    --cc=yosryahmed@google.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

all inboxes | Powered by JetHome®