Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: <kevin.tian@intel.com>, <robin.murphy@arm.com>, <joro@8bytes.org>,
	<will@kernel.org>, <shuah@kernel.org>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] iommufd: Reorder include files
Date: Thu, 15 Aug 2024 11:12:06 -0700	[thread overview]
Message-ID: <Zr5E9jlQ0HJt0BGE@Asurada-Nvidia> (raw)
In-Reply-To: <20240815175140.GM2032816@nvidia.com>

On Thu, Aug 15, 2024 at 02:51:40PM -0300, Jason Gunthorpe wrote:
> On Fri, Aug 02, 2024 at 05:32:02PM -0700, Nicolin Chen wrote:
> > Reorder include files to alphabetic order to simplify maintenance, and
> > separate local headers and global headers with a blank line.
> > 
> > No functional change intended.
> > 
> > Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
> > ---
> >  drivers/iommu/iommufd/device.c          |  4 ++--
> >  drivers/iommu/iommufd/fault.c           |  4 ++--
> >  drivers/iommu/iommufd/io_pagetable.c    |  8 ++++----
> >  drivers/iommu/iommufd/io_pagetable.h    |  2 +-
> >  drivers/iommu/iommufd/ioas.c            |  2 +-
> >  drivers/iommu/iommufd/iommufd_private.h |  9 +++++----
> >  drivers/iommu/iommufd/iommufd_test.h    |  2 +-
> >  drivers/iommu/iommufd/iova_bitmap.c     |  2 +-
> >  drivers/iommu/iommufd/main.c            |  8 ++++----
> >  drivers/iommu/iommufd/pages.c           | 10 +++++-----
> >  drivers/iommu/iommufd/selftest.c        |  8 ++++----
> >  include/linux/iommufd.h                 |  4 ++--
> >  include/uapi/linux/iommufd.h            |  2 +-
> >  13 files changed, 33 insertions(+), 32 deletions(-)
> 
> I picked this on up to iommufd for-next

Thanks! Was hoping for that.

> When you get an answer if we can do something else for the MSI lets
> reconsider that patch, also the 3rd one has a kbuild failure.

Yea, let's hold the other patches in this series. I will submit
another selftest patch, after we have an alternative solution.

Nicolin

  reply	other threads:[~2024-08-15 18:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-03  0:32 [PATCH v2 0/3] iommufd: Add selftest coverage for reserved IOVAs Nicolin Chen
2024-08-03  0:32 ` [PATCH v2 1/3] iommufd: Reorder include files Nicolin Chen
2024-08-15 17:51   ` Jason Gunthorpe
2024-08-15 18:12     ` Nicolin Chen [this message]
2024-08-03  0:32 ` [PATCH v2 2/3] iommu/dma: Support MSIs through nested domains Nicolin Chen
2024-08-06  8:25   ` Tian, Kevin
2024-08-06 17:24     ` Nicolin Chen
2024-08-08 12:38     ` Robin Murphy
2024-08-08 22:59       ` Nicolin Chen
2024-08-09  8:00         ` Tian, Kevin
2024-08-09 17:43           ` Robin Murphy
2024-08-09 20:09             ` Nicolin Chen
2024-08-09 23:01           ` Jason Gunthorpe
2024-08-09  7:34       ` Tian, Kevin
2024-08-09 18:41       ` Jason Gunthorpe
2024-08-09 19:18         ` Nicolin Chen
2024-08-09 22:49           ` Jason Gunthorpe
2024-08-09 23:38             ` Nicolin Chen
2024-08-03  0:32 ` [PATCH v2 3/3] iommufd/selftest: Add coverage for reserved IOVAs Nicolin Chen
2024-08-09 15:52   ` kernel test robot

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=Zr5E9jlQ0HJt0BGE@Asurada-Nvidia \
    --to=nicolinc@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=shuah@kernel.org \
    --cc=will@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