From: kernel test robot <lkp@intel.com>
To: Zhenhua Huang <quic_zhenhuah@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@quicinc.com, quic_tingweiz@quicinc.com,
Zhenhua Huang <quic_zhenhuah@quicinc.com>
Subject: Re: [PATCH v1 3/5] soc: qcom: memory_dump: Add memory dump driver
Date: Fri, 27 Oct 2023 02:58:40 +0800 [thread overview]
Message-ID: <202310270221.jqcwE137-lkp@intel.com> (raw)
In-Reply-To: <1698052857-6918-4-git-send-email-quic_zhenhuah@quicinc.com>
Hi Zhenhua,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on arm64/for-next/core linus/master v6.6-rc7 next-20231026]
[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/Zhenhua-Huang/dt-bindings-soc-qcom-Add-memory_dump-driver-bindings/20231023-172245
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/1698052857-6918-4-git-send-email-quic_zhenhuah%40quicinc.com
patch subject: [PATCH v1 3/5] soc: qcom: memory_dump: Add memory dump driver
reproduce: (https://download.01.org/0day-ci/archive/20231027/202310270221.jqcwE137-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/202310270221.jqcwE137-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: MAINTAINERS references a file that doesn't exist: Documentation/devicetree/bindings/soc/qcom/qcom,memory_dump.yaml
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-26 18:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 9:20 [PATCH v1 0/5] soc/arm64: qcom: add initial version of memory dump Zhenhua Huang
2023-10-23 9:20 ` [PATCH v1 1/5] dt-bindings: soc: qcom: Add memory_dump driver bindings Zhenhua Huang
2023-10-23 9:27 ` Krzysztof Kozlowski
2023-10-23 11:54 ` Zhenhua Huang
2023-10-23 12:52 ` Krzysztof Kozlowski
2023-10-24 10:57 ` Zhenhua Huang
2023-10-24 13:55 ` Krzysztof Kozlowski
2023-10-26 21:01 ` Elliot Berman
2023-10-23 17:40 ` Rob Herring
2023-10-23 9:20 ` [PATCH v1 2/5] dt-bindings: sram: qcom,imem: document sm8250 Zhenhua Huang
2023-10-23 9:27 ` Krzysztof Kozlowski
2023-10-23 17:40 ` Rob Herring
2023-10-24 11:07 ` Zhenhua Huang
2023-10-23 9:20 ` [PATCH v1 3/5] soc: qcom: memory_dump: Add memory dump driver Zhenhua Huang
2023-10-23 9:31 ` Krzysztof Kozlowski
2023-10-23 11:43 ` Zhenhua Huang
2023-10-23 11:46 ` Krzysztof Kozlowski
2023-10-23 12:19 ` Zhenhua Huang
2023-10-23 12:53 ` Krzysztof Kozlowski
2023-10-24 10:57 ` Zhenhua Huang
2023-10-24 13:58 ` Krzysztof Kozlowski
2023-10-23 13:56 ` Konrad Dybcio
2023-10-24 7:36 ` Zhenhua Huang
2023-10-26 18:58 ` kernel test robot [this message]
2023-10-23 9:20 ` [PATCH v1 4/5] arm64: defconfig: enable Qcom Memory Dump driver Zhenhua Huang
2023-10-23 9:32 ` Krzysztof Kozlowski
2023-10-23 11:43 ` Zhenhua Huang
2023-10-23 11:47 ` Krzysztof Kozlowski
2023-10-23 12:19 ` Zhenhua Huang
2023-10-23 9:20 ` [PATCH v1 5/5] arm64: dts: qcom: sm8250: Add memory dump node Zhenhua Huang
2023-10-23 9:33 ` Krzysztof Kozlowski
2023-10-23 9:25 ` [PATCH v1 0/5] soc/arm64: qcom: add initial version of memory dump Krzysztof Kozlowski
2023-10-23 12:18 ` Zhenhua Huang
2023-10-23 12:54 ` Krzysztof Kozlowski
2023-10-23 13:50 ` Konrad Dybcio
2023-10-24 10:10 ` Zhenhua Huang
2023-10-24 14:25 ` Jeff Johnson
2023-10-23 14:31 ` Caleb Connolly
2023-10-24 9:53 ` Zhenhua Huang
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=202310270221.jqcwE137-lkp@intel.com \
--to=lkp@intel.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_zhenhuah@quicinc.com \
--cc=robh+dt@kernel.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