oe-kbuild-all.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ohad Sharabi <osharabi@habana.ai>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Oded Gabbay <ogabbay@kernel.org>
Subject: [linux-next:master 5896/6975] drivers/accel/habanalabs/common/device.c:209:37: error: 'struct scatterlist' has no member named 'dma_length'; did you mean 'length'?
Date: Thu, 21 Sep 2023 17:54:01 +0800	[thread overview]
Message-ID: <202309211712.ti68BWbS-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   940fcc189c51032dd0282cbee4497542c982ac59
commit: c313fc57eaefbeca50a51d5d2554264297d98526 [5896/6975] accel/habanalabs: trace dma map sgtable
config: um-randconfig-r005-20230815 (https://download.01.org/0day-ci/archive/20230921/202309211712.ti68BWbS-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230921/202309211712.ti68BWbS-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/202309211712.ti68BWbS-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/accel/habanalabs/common/device.c: In function 'hl_dma_map_sgtable_caller':
>> drivers/accel/habanalabs/common/device.c:209:37: error: 'struct scatterlist' has no member named 'dma_length'; did you mean 'length'?
     209 |                                 sg->dma_length, dir, caller);
         |                                     ^~~~~~~~~~
         |                                     length
   drivers/accel/habanalabs/common/device.c: In function 'hl_dma_unmap_sgtable_caller':
   drivers/accel/habanalabs/common/device.c:246:45: error: 'struct scatterlist' has no member named 'dma_length'; did you mean 'length'?
     246 |                                         sg->dma_length, dir, caller);
         |                                             ^~~~~~~~~~
         |                                             length


vim +209 drivers/accel/habanalabs/common/device.c

   190	
   191	int hl_dma_map_sgtable_caller(struct hl_device *hdev, struct sg_table *sgt,
   192					enum dma_data_direction dir, const char *caller)
   193	{
   194		struct asic_fixed_properties *prop = &hdev->asic_prop;
   195		struct scatterlist *sg;
   196		int rc, i;
   197	
   198		rc = hdev->asic_funcs->dma_map_sgtable(hdev, sgt, dir);
   199		if (rc)
   200			return rc;
   201	
   202		if (!trace_habanalabs_dma_map_page_enabled())
   203			return 0;
   204	
   205		for_each_sgtable_dma_sg(sgt, sg, i)
   206			trace_habanalabs_dma_map_page(hdev->dev,
   207					page_to_phys(sg_page(sg)),
   208					sg->dma_address - prop->device_dma_offset_for_host_access,
 > 209					sg->dma_length, dir, caller);
   210	
   211		return 0;
   212	}
   213	

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

                 reply	other threads:[~2023-09-21  9:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202309211712.ti68BWbS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ogabbay@kernel.org \
    --cc=osharabi@habana.ai \
    /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).