mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
To: kernel test robot <lkp@intel.com>, rafael@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, daniel.lezcano@linaro.org,
	rui.zhang@intel.com, lukasz.luba@arm.com,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com, wenst@chromium.org
Subject: Re: [PATCH] thermal: Add support for device tree thermal zones consumers
Date: Wed, 15 Nov 2023 15:45:59 +0100	[thread overview]
Message-ID: <8e40838f-1a72-4167-8ff5-0ca1584e0246@collabora.com> (raw)
In-Reply-To: <202311152230.nzJVHaeG-lkp@intel.com>

Il 15/11/23 15:37, kernel test robot ha scritto:
> Hi AngeloGioacchino,
> 
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on rafael-pm/thermal]
> [also build test ERROR on linus/master v6.7-rc1 next-20231115]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/AngeloGioacchino-Del-Regno/thermal-Add-support-for-device-tree-thermal-zones-consumers/20231114-211656
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git thermal
> patch link:    https://lore.kernel.org/r/20231114131514.89031-1-angelogioacchino.delregno%40collabora.com
> patch subject: [PATCH] thermal: Add support for device tree thermal zones consumers
> config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20231115/202311152230.nzJVHaeG-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/20231115/202311152230.nzJVHaeG-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/202311152230.nzJVHaeG-lkp@intel.com/

..snip..

> 
> 
> vim +282 include/linux/thermal.h
> 
>     280	

That's right, I forgot to add "static inline" :-)

Fixing and sending a v2.

>     281	struct thermal_zone_device *thermal_of_get_zone_by_index(struct device *dev, int index)
>   > 282	{
>     283		return ERR_PTR(-EOPNOTSUPP);
>     284	}
>     285	
>     286	struct thermal_zone_device *thermal_of_get_zone(struct device *dev, const char *name)
>   > 287	{
>     288		return ERR_PTR(-EOPNOTSUPP);
>     289	}
>     290	#endif
>     291	
> 




  reply	other threads:[~2023-11-15 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 13:15 AngeloGioacchino Del Regno
2023-11-15 14:37 ` kernel test robot
2023-11-15 14:45   ` AngeloGioacchino Del Regno [this message]
2023-11-15 15:01 ` kernel test robot
2023-11-15 15:01 ` 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=8e40838f-1a72-4167-8ff5-0ca1584e0246@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lukasz.luba@arm.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=wenst@chromium.org \
    /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®