From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
Cornelia Huck <cohuck@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/8] vfio: Add header guards and includes to drivers/vfio/vfio.h
Date: Wed, 31 Aug 2022 15:24:40 -0300 [thread overview]
Message-ID: <Yw+naMPLU9gD0oTR@nvidia.com> (raw)
In-Reply-To: <20220831120231.320081f0.alex.williamson@redhat.com>
On Wed, Aug 31, 2022 at 12:02:31PM -0600, Alex Williamson wrote:
> > The criteria I like to use is if the header is able to compile
> > stand-alone.
>
> Is this stream of consciousness or is there some tooling for this? ;)
In my case I'm using clangd https://clangd.llvm.org/ in the editor,
which checks header files for self-consistency.
But there is also https://include-what-you-use.org/ (though I have
never tried it)
But the above wack of text is just the normal compiler invocation of
vfio_main.c with main.c replaced by the header.
> > > btw while they are moved here the inclusions in vfio_main.c are
> > > not removed in patch8.
> >
> > ? I'm not sure I understand this
>
> I think Kevin is asking why these includes were not also removed from
> vfio_main.c when adding them to vfio.h. Thanks,
Oh, I am actually unclear what is policy/preference/consensus in that
area.
I know a strong camp is to avoid implicit includes, so the duplicated
includes are welcomed. include-what-you-use for instance is that
philosophy.
Do you have a preference?
Jason
next prev parent reply other threads:[~2022-08-31 18:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 1:01 [PATCH 0/8] vfio: Split the container code into a clean layer and dedicated file Jason Gunthorpe
2022-08-31 1:01 ` [PATCH 1/8] vfio: Add header guards and includes to drivers/vfio/vfio.h Jason Gunthorpe
2022-08-31 8:42 ` Tian, Kevin
2022-08-31 15:36 ` Jason Gunthorpe
2022-08-31 18:02 ` Alex Williamson
2022-08-31 18:24 ` Jason Gunthorpe [this message]
2022-09-01 2:17 ` Tian, Kevin
2022-08-31 1:01 ` [PATCH 2/8] vfio: Rename __vfio_group_unset_container() Jason Gunthorpe
2022-08-31 8:46 ` Tian, Kevin
2022-09-02 0:28 ` Jason Gunthorpe
2022-09-02 3:51 ` Tian, Kevin
2022-09-02 14:39 ` Alex Williamson
2022-09-02 16:24 ` Jason Gunthorpe
2022-09-06 3:35 ` Tian, Kevin
2022-09-06 19:38 ` Alex Williamson
2022-09-06 23:06 ` Jason Gunthorpe
2022-08-31 1:01 ` [PATCH 3/8] vfio: Split the container logic into vfio_container_attach_group() Jason Gunthorpe
2022-08-31 8:47 ` Tian, Kevin
2022-09-02 0:42 ` Jason Gunthorpe
2022-08-31 1:01 ` [PATCH 4/8] vfio: Remove #ifdefs around CONFIG_VFIO_NOIOMMU Jason Gunthorpe
2022-08-31 8:48 ` Tian, Kevin
2022-08-31 15:28 ` Jason Gunthorpe
2022-09-01 2:18 ` Tian, Kevin
2022-08-31 1:01 ` [PATCH 5/8] vfio: Split out container code from the init/cleanup functions Jason Gunthorpe
2022-08-31 8:49 ` Tian, Kevin
2022-08-31 1:02 ` [PATCH 6/8] vfio: Rename vfio_ioctl_check_extension() Jason Gunthorpe
2022-08-31 8:50 ` Tian, Kevin
2022-08-31 1:02 ` [PATCH 7/8] vfio: Split the register_device ops call into functions Jason Gunthorpe
2022-09-02 3:52 ` Tian, Kevin
2022-08-31 1:02 ` [PATCH 8/8] vfio: Move container code into drivers/vfio/container.c Jason Gunthorpe
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=Yw+naMPLU9gD0oTR@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.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).