public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: kernel test robot <lkp@intel.com>,
	Hsiao Chien Sung <shawn.sung@mediatek.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [mediatek:v6.7-tmp/soc 7/7] drivers/soc/mediatek/mt8188-mmsys.h:126:3: error: use of undeclared identifier 'MT8188_VDO0_RST_DISP_OVL0'
Date: Tue, 21 Nov 2023 12:39:58 +0100	[thread overview]
Message-ID: <060248c3-38c0-4896-b01a-59c19ff7c6d6@collabora.com> (raw)
In-Reply-To: <202311211559.hXmHshEO-lkp@intel.com>

Il 21/11/23 08:21, kernel test robot ha scritto:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux.git v6.7-tmp/soc
> head:   c1b652b84e6a779e670bac250d80ef2f2d4a45d9
> commit: c1b652b84e6a779e670bac250d80ef2f2d4a45d9 [7/7] soc: mediatek: Add MT8188 VDOSYS reset bit map
> config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20231121/202311211559.hXmHshEO-lkp@intel.com/config)
> compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231121/202311211559.hXmHshEO-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/202311211559.hXmHshEO-lkp@intel.com/
> 

No action required. This is because this branch needs commits from v6.7-tmp/dts64.


      reply	other threads:[~2023-11-21 11:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21  7:21 [mediatek:v6.7-tmp/soc 7/7] drivers/soc/mediatek/mt8188-mmsys.h:126:3: error: use of undeclared identifier 'MT8188_VDO0_RST_DISP_OVL0' kernel test robot
2023-11-21 11:39 ` AngeloGioacchino Del Regno [this message]

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=060248c3-38c0-4896-b01a-59c19ff7c6d6@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=shawn.sung@mediatek.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