mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Zack Rusin <zackr@vmware.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Martin Krastev <krastevm@vmware.com>,
	Maaz Mombasawala <mombasawalam@vmware.com>
Subject: drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c:76: warning: Excess struct member 'transfer' description in 'vmw_stdu_dirty'
Date: Fri, 15 Dec 2023 03:54:44 +0800	[thread overview]
Message-ID: <202312150347.5icezNlK-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   5bd7ef53ffe5ca580e93e74eb8c81ed191ddc4bd
commit: 39985eea5a6dd1e844f216028252870e980b9e7f drm/vmwgfx: Abstract placement selection
date:   10 months ago
config: i386-buildonly-randconfig-004-20231214 (https://download.01.org/0day-ci/archive/20231215/202312150347.5icezNlK-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231215/202312150347.5icezNlK-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/202312150347.5icezNlK-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c:76: warning: Excess struct member 'transfer' description in 'vmw_stdu_dirty'


vim +76 drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c

35c051258e8fd7 Sinclair Yeh     2015-06-26  51  
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  52  /**
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  53   * struct vmw_stdu_dirty - closure structure for the update functions
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  54   *
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  55   * @base: The base type we derive from. Used by vmw_kms_helper_dirty().
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  56   * @transfer: Transfer direction for DMA command.
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  57   * @left: Left side of bounding box.
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  58   * @right: Right side of bounding box.
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  59   * @top: Top side of bounding box.
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  60   * @bottom: Bottom side of bounding box.
a1ac6339123051 Sinclair Yeh     2017-06-02  61   * @fb_left: Left side of the framebuffer/content bounding box
a1ac6339123051 Sinclair Yeh     2017-06-02  62   * @fb_top: Top of the framebuffer/content bounding box
1856a91691e40e Lee Jones        2021-01-15  63   * @pitch: framebuffer pitch (stride)
f1d34bfd70b1b4 Thomas Hellstrom 2018-06-19  64   * @buf: buffer object when DMA-ing between buffer and screen targets.
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  65   * @sid: Surface ID when copying between surface and screen targets.
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  66   */
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  67  struct vmw_stdu_dirty {
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  68  	struct vmw_kms_dirty base;
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  69  	s32 left, right, top, bottom;
a1ac6339123051 Sinclair Yeh     2017-06-02  70  	s32 fb_left, fb_top;
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  71  	u32 pitch;
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  72  	union {
09881d2940bbd6 Zack Rusin       2023-01-30  73  		struct vmw_bo *buf;
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  74  		u32 sid;
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  75  	};
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26 @76  };
6bf6bf03b37b5b Thomas Hellstrom 2015-06-26  77  

:::::: The code at line 76 was first introduced by commit
:::::: 6bf6bf03b37b5ba0f3399fa9bb3d62edfa117c87 drm/vmwgfx: Convert screen targets to new helpers v3

:::::: TO: Thomas Hellstrom <thellstrom@vmware.com>
:::::: CC: Thomas Hellstrom <thellstrom@vmware.com>

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

                 reply	other threads:[~2023-12-14 19:55 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=202312150347.5icezNlK-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=krastevm@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mombasawalam@vmware.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=zackr@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®