All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dave Airlie <airlied@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [geert-renesas-drivers:master 17/54] drivers/gpu/drm/bridge/lontium-lt9611.c:1147:10: error: no member named 'audio_pdev' in 'struct lt9611'
Date: Wed, 15 Jan 2025 07:09:24 +0800	[thread overview]
Message-ID: <202501150653.OSZGL4LT-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git master
head:   d088502a519fb7834bf6e34cb4e531c1e8113bd1
commit: b49bbb5dbe7654f0d7996206f543d91bbed33569 [17/54] Merge remote-tracking branch 'drm/drm-next' into renesas-drivers
config: hexagon-randconfig-001-20250115 (https://download.01.org/0day-ci/archive/20250115/202501150653.OSZGL4LT-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project f5cd181ffbb7cb61d582fe130d46580d5969d47a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250115/202501150653.OSZGL4LT-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/202501150653.OSZGL4LT-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/gpu/drm/bridge/lontium-lt9611.c:1147:10: error: no member named 'audio_pdev' in 'struct lt9611'
    1147 |         lt9611->audio_pdev =
         |         ~~~~~~  ^
   drivers/gpu/drm/bridge/lontium-lt9611.c:1152:33: error: no member named 'audio_pdev' in 'struct lt9611'
    1152 |         return PTR_ERR_OR_ZERO(lt9611->audio_pdev);
         |                                ~~~~~~  ^
   drivers/gpu/drm/bridge/lontium-lt9611.c:1157:14: error: no member named 'audio_pdev' in 'struct lt9611'
    1157 |         if (lt9611->audio_pdev) {
         |             ~~~~~~  ^
   drivers/gpu/drm/bridge/lontium-lt9611.c:1158:38: error: no member named 'audio_pdev' in 'struct lt9611'
    1158 |                 platform_device_unregister(lt9611->audio_pdev);
         |                                            ~~~~~~  ^
   drivers/gpu/drm/bridge/lontium-lt9611.c:1159:11: error: no member named 'audio_pdev' in 'struct lt9611'
    1159 |                 lt9611->audio_pdev = NULL;
         |                 ~~~~~~  ^
   5 errors generated.


vim +1147 drivers/gpu/drm/bridge/lontium-lt9611.c

23278bf54afe18 Vinod Koul 2020-07-23  1143  
23278bf54afe18 Vinod Koul 2020-07-23  1144  static int lt9611_audio_init(struct device *dev, struct lt9611 *lt9611)
23278bf54afe18 Vinod Koul 2020-07-23  1145  {
23278bf54afe18 Vinod Koul 2020-07-23  1146  	codec_data.data = lt9611;
23278bf54afe18 Vinod Koul 2020-07-23 @1147  	lt9611->audio_pdev =
23278bf54afe18 Vinod Koul 2020-07-23  1148  		platform_device_register_data(dev, HDMI_CODEC_DRV_NAME,
23278bf54afe18 Vinod Koul 2020-07-23  1149  					      PLATFORM_DEVID_AUTO,
23278bf54afe18 Vinod Koul 2020-07-23  1150  					      &codec_data, sizeof(codec_data));
23278bf54afe18 Vinod Koul 2020-07-23  1151  
23278bf54afe18 Vinod Koul 2020-07-23  1152  	return PTR_ERR_OR_ZERO(lt9611->audio_pdev);
23278bf54afe18 Vinod Koul 2020-07-23  1153  }
23278bf54afe18 Vinod Koul 2020-07-23  1154  

:::::: The code at line 1147 was first introduced by commit
:::::: 23278bf54afe180967069bdc8c0f1c7a365fc63e drm/bridge: Introduce LT9611 DSI to HDMI bridge

:::::: TO: Vinod Koul <vkoul@kernel.org>
:::::: CC: Sam Ravnborg <sam@ravnborg.org>

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

                 reply	other threads:[~2025-01-14 23:09 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=202501150653.OSZGL4LT-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=airlied@redhat.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --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 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.