All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC v2 3/7] drm/connector: implement generic HDMI codec helpers
Date: Sat, 2 Nov 2024 15:49:26 +0800	[thread overview]
Message-ID: <202411021500.tp7G2CnS-lkp@intel.com> (raw)
In-Reply-To: <20241101-drm-bridge-hdmi-connector-v2-3-739ef9addf9e@linaro.org>

Hi Dmitry,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on f9f24ca362a4d84dd8aeb4b8f3ec28cb6c43dd06]

url:    https://github.com/intel-lab-lkp/linux/commits/Dmitry-Baryshkov/ASoC-hdmi-codec-pass-data-to-get_dai_id-too/20241101-182046
base:   f9f24ca362a4d84dd8aeb4b8f3ec28cb6c43dd06
patch link:    https://lore.kernel.org/r/20241101-drm-bridge-hdmi-connector-v2-3-739ef9addf9e%40linaro.org
patch subject: [PATCH RFC v2 3/7] drm/connector: implement generic HDMI codec helpers
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20241102/202411021500.tp7G2CnS-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/20241102/202411021500.tp7G2CnS-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/202411021500.tp7G2CnS-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/drm_connector_hdmi_codec.c:161: warning: expecting prototype for drm_connector_hdmi_init(). Prototype was for drm_connector_hdmi_codec_init() instead


vim +161 drivers/gpu/drm/drm_connector_hdmi_codec.c

   150	
   151	/**
   152	 * drm_connector_hdmi_init - Initialize HDMI Codec device for the DRM connector
   153	 * @connector: A pointer to the connector to allocate codec for
   154	 *
   155	 * Create a HDMI codec device to be used with the specified connector.
   156	 *
   157	 * Returns:
   158	 * Zero on success, error code on failure.
   159	 */
   160	int drm_connector_hdmi_codec_init(struct drm_connector *connector)
 > 161	{

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

  reply	other threads:[~2024-11-02  7:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 10:19 [PATCH RFC v2 0/7] drm: add DRM HDMI Codec framework Dmitry Baryshkov
2024-11-01 10:19 ` Dmitry Baryshkov
2024-11-01 10:19 ` [PATCH RFC v2 1/7] ASoC: hdmi-codec: pass data to get_dai_id too Dmitry Baryshkov
2024-11-01 10:19   ` Dmitry Baryshkov
2024-11-01 10:19 ` [PATCH RFC v2 2/7] ASoC: hdmi-codec: move no_capture_mute to struct hdmi_codec_pdata Dmitry Baryshkov
2024-11-01 10:19   ` Dmitry Baryshkov
2024-11-01 19:26   ` Mark Brown
2024-11-01 19:26     ` Mark Brown
2024-11-01 10:19 ` [PATCH RFC v2 3/7] drm/connector: implement generic HDMI codec helpers Dmitry Baryshkov
2024-11-01 10:19   ` Dmitry Baryshkov
2024-11-02  7:49   ` kernel test robot [this message]
2024-11-01 10:19 ` [PATCH RFC v2 4/7] drm/bridge: connector: add support for HDMI codec framework Dmitry Baryshkov
2024-11-01 10:19   ` Dmitry Baryshkov
2024-11-01 10:19 ` [PATCH RFC v2 5/7] drm/bridge: lt9611: switch to using the DRM " Dmitry Baryshkov
2024-11-01 10:19   ` Dmitry Baryshkov
2024-11-01 10:19 ` [PATCH RFC v2 6/7] drm/display/hdmi: implement connector update functions Dmitry Baryshkov
2024-11-01 10:19   ` Dmitry Baryshkov
2024-11-01 10:59   ` Jani Nikula
2024-11-01 10:59     ` Jani Nikula
2024-11-01 12:09     ` Dmitry Baryshkov
2024-11-01 12:09       ` Dmitry Baryshkov
2024-11-01 10:19 ` [PATCH RFC v2 7/7] drm/bridge_connector: hook __drm_atomic_helper_connector_hdmi_update_edid() Dmitry Baryshkov
2024-11-01 10:19   ` Dmitry Baryshkov

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=202411021500.tp7G2CnS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dmitry.baryshkov@linaro.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 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.