From: Nitin <nitjoshi@gmail.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: kernel test robot <lkp@intel.com>,
Hans de Goede <hansg@kernel.org>,
oe-kbuild-all@lists.linux.dev,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
njoshi1@lenovo.com, Mark Pearson <mpearson-lenovo@squebb.ca>
Subject: Re: [PATCH v2 1/2] platform/x86: thinkpad_acpi: Add support to detect hardware damage detection capability.
Date: Tue, 16 Dec 2025 20:15:04 +0900 [thread overview]
Message-ID: <1ca74be1-7b4c-4a38-b507-f320104a7a60@gmail.com> (raw)
In-Reply-To: <2433802f-ba32-1549-41f1-5a77e998c139@linux.intel.com>
On 12/16/25 19:19, Ilpo Järvinen wrote:
> On Tue, 16 Dec 2025, Nitin wrote:
>
>> Hello ,
>>
>> On 12/16/25 10:19, kernel test robot wrote:
>>> Hi Nitin,
>>>
>>> kernel test robot noticed the following build warnings:
>>>
>>> [auto build test WARNING on linus/master]
>>> [also build test WARNING on v6.19-rc1 next-20251215]
>>> [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/Nitin-Joshi/platform-x86-thinkpad_acpi-Add-sysfs-to-display-details-of-damaged-device/20251210-231409
>>> base: linus/master
>>> patch link:
>>> https://lore.kernel.org/r/20251210151133.7933-1-nitjoshi%40gmail.com
>>> patch subject: [PATCH v2 1/2] platform/x86: thinkpad_acpi: Add support to
>>> detect hardware damage detection capability.
>>> reproduce:
>>> (https://download.01.org/0day-ci/archive/20251216/202512160219.94nMjvxO-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/202512160219.94nMjvxO-lkp@intel.com/
>> Thank you for reporting this issue and I will fix this issue .
>>
>> I have already send patch v3 for this and will fix this warning in next patch
>> version i.e v4 .
>>
>> May i know, if its OK to add this Reported-by and closes tag in patch version
>> v4 ?
> Hi,
>
> Please only add those tags when you're fixing code that exists in a repo
> already. For new work, we don't normally add lkp report tags despite the
> email suggesting you to do so (I know it's a bit confusing but it's sort
> of same as we don't normally mention all reviewers who gave improvement
> suggestions either).
Noted, Thank you for clarification . I will send next patch revision soon.
Thank you !
>>> All warnings (new ones prefixed by >>):
>>>
>>> WARNING: No kernel-doc for file ./include/linux/pci.h
>>> ERROR: Cannot find file ./include/linux/mod_devicetable.h
>>> WARNING: No kernel-doc for file ./include/linux/mod_devicetable.h
>>> ERROR: Cannot find file ./include/linux/bootconfig.h
>>> WARNING: No kernel-doc for file ./include/linux/bootconfig.h
>>>>> Documentation/admin-guide/laptops/thinkpad-acpi.rst:1581: WARNING: Title
>>>>> underline too short.
>>> --
>>> Hardware damage detection capability
>>> ----------------- [docutils]
>>>>> Documentation/admin-guide/laptops/thinkpad-acpi.rst:1581: WARNING: Title
>>>>> underline too short.
>> Ack. Thank you !
>>
>>> vim +1581 Documentation/admin-guide/laptops/thinkpad-acpi.rst
>>>
>>> 1579
>>> 1580 Hardware damage detection capability
>>>> 1581 -----------------
>>> 1582
>>>
prev parent reply other threads:[~2025-12-16 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 15:11 Nitin Joshi
2025-12-10 15:11 ` [PATCH v2 2/2] platform/x86: thinkpad_acpi: Add sysfs to display details of damaged device Nitin Joshi
2025-12-10 15:43 ` Mario Limonciello
2025-12-10 16:27 ` Nitin
2025-12-10 16:44 ` Mario Limonciello
2025-12-10 16:52 ` Nitin
2025-12-16 4:42 ` kernel test robot
2025-12-16 1:19 ` [PATCH v2 1/2] platform/x86: thinkpad_acpi: Add support to detect hardware damage detection capability kernel test robot
2025-12-16 2:29 ` Nitin
2025-12-16 10:19 ` Ilpo Järvinen
2025-12-16 11:15 ` Nitin [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=1ca74be1-7b4c-4a38-b507-f320104a7a60@gmail.com \
--to=nitjoshi@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=njoshi1@lenovo.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=platform-driver-x86@vger.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
all inboxes | Powered by JetHome®