linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Joao Martins <joao.m.martins@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Kevin Tian <kevin.tian@intel.com>
Subject: [linux-next:master 11303/14422] include/linux/io-pgtable.h:172:44: warning: 'struct iommu_dirty_bitmap' declared inside parameter list will not be visible outside of this definition or declaration
Date: Mon, 23 Oct 2023 21:53:39 +0800	[thread overview]
Message-ID: <202310232131.TOhkKzZa-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   e8361b005d7c92997d12f2b85a9e4a525738bd9d
commit: 14207f68dddf152fd0b2916451a1f4702de886e4 [11303/14422] iommu: Add iommu_domain ops for dirty tracking
config: sparc64-randconfig-r002-20220915 (https://download.01.org/0day-ci/archive/20231023/202310232131.TOhkKzZa-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231023/202310232131.TOhkKzZa-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310232131.TOhkKzZa-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/iommu/io-pgtable.c:11:
>> include/linux/io-pgtable.h:172:44: warning: 'struct iommu_dirty_bitmap' declared inside parameter list will not be visible outside of this definition or declaration
     172 |                                     struct iommu_dirty_bitmap *dirty);
         |                                            ^~~~~~~~~~~~~~~~~~


vim +172 include/linux/io-pgtable.h

   149	
   150	/**
   151	 * struct io_pgtable_ops - Page table manipulation API for IOMMU drivers.
   152	 *
   153	 * @map_pages:    Map a physically contiguous range of pages of the same size.
   154	 * @unmap_pages:  Unmap a range of virtually contiguous pages of the same size.
   155	 * @iova_to_phys: Translate iova to physical address.
   156	 *
   157	 * These functions map directly onto the iommu_ops member functions with
   158	 * the same names.
   159	 */
   160	struct io_pgtable_ops {
   161		int (*map_pages)(struct io_pgtable_ops *ops, unsigned long iova,
   162				 phys_addr_t paddr, size_t pgsize, size_t pgcount,
   163				 int prot, gfp_t gfp, size_t *mapped);
   164		size_t (*unmap_pages)(struct io_pgtable_ops *ops, unsigned long iova,
   165				      size_t pgsize, size_t pgcount,
   166				      struct iommu_iotlb_gather *gather);
   167		phys_addr_t (*iova_to_phys)(struct io_pgtable_ops *ops,
   168					    unsigned long iova);
   169		int (*read_and_clear_dirty)(struct io_pgtable_ops *ops,
   170					    unsigned long iova, size_t size,
   171					    unsigned long flags,
 > 172					    struct iommu_dirty_bitmap *dirty);
   173	};
   174	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2023-10-23 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 13:53 kernel test robot [this message]
2023-10-23 16:14 ` Joao Martins

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=202310232131.TOhkKzZa-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=joao.m.martins@oracle.com \
    --cc=kevin.tian@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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