All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Ville Syrjälä " <ville.syrjala@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [vsyrjala:remap_tile_ys_64 18/30] drivers/gpu/drm/i915/i915_vma.c:968:1: error: conflicting types for 'add_pages'; have 'struct scatterlist *(dma_addr_t,  unsigned int,  struct sg_table *, struct scatterlist *)' {aka 'struct scatterlist *(long long unsigned int,  unsigned int,  struct sg_...
Date: Wed, 08 Apr 2026 03:42:03 +0200	[thread overview]
Message-ID: <202604080343.eLWuZISe-lkp@intel.com> (raw)

tree:   https://github.com/vsyrjala/linux.git remap_tile_ys_64
head:   9a8f5dc5c6e5da24a2df0e93fda770ab217b0886
commit: 539e2225c8d7e19d4095bace6c48ec8d3d434e93 [18/30] drm/i915/vma: Extract add_pages()
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260408/202604080343.eLWuZISe-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260408/202604080343.eLWuZISe-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/202604080343.eLWuZISe-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/i915/i915_vma.c:968:1: error: conflicting types for 'add_pages'; have 'struct scatterlist *(dma_addr_t,  unsigned int,  struct sg_table *, struct scatterlist *)' {aka 'struct scatterlist *(long long unsigned int,  unsigned int,  struct sg_table *, struct scatterlist *)'}
     968 | add_pages(dma_addr_t addr, unsigned int count,
         | ^~~~~~~~~
   In file included from include/linux/mmzone.h:1534,
                    from include/linux/gfp.h:7,
                    from include/linux/sched/mm.h:9,
                    from drivers/gpu/drm/i915/i915_vma.c:25:
   include/linux/memory_hotplug.h:153:5: note: previous declaration of 'add_pages' with type 'int(int,  long unsigned int,  long unsigned int,  struct mhp_params *)'
     153 | int add_pages(int nid, unsigned long start_pfn, unsigned long nr_pages,
         |     ^~~~~~~~~


vim +968 drivers/gpu/drm/i915/i915_vma.c

   966	
   967	static struct scatterlist *
 > 968	add_pages(dma_addr_t addr, unsigned int count,
   969		  struct sg_table *st, struct scatterlist *sg)
   970	{
   971		st->nents++;
   972	
   973		sg_set_page(sg, NULL, count * I915_GTT_PAGE_SIZE, 0);
   974		sg_dma_address(sg) = addr;
   975		sg_dma_len(sg) = count * I915_GTT_PAGE_SIZE;
   976	
   977		return sg_next(sg);
   978	}
   979	

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

             reply	other threads:[~2026-04-08  1:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08  1:42 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-08 12:02 [vsyrjala:remap_tile_ys_64 18/30] drivers/gpu/drm/i915/i915_vma.c:968:1: error: conflicting types for 'add_pages'; have 'struct scatterlist *(dma_addr_t, unsigned int, struct sg_table *, struct scatterlist *)' {aka 'struct scatterlist *(long long unsigned int, unsigned int, struct sg_ 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=202604080343.eLWuZISe-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ville.syrjala@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.