From: Randy Dunlap <rdunlap@infradead.org>
To: Hans de Goede <hdegoede@redhat.com>, kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
linux-doc@vger.kernel.org
Subject: Re: [linux-next:master 12610/12662] htmldocs: Warning: file Documentation/ABI/testing/sysfs-platform-silicom#20:
Date: Sun, 4 Feb 2024 07:40:12 -0800 [thread overview]
Message-ID: <7531b72b-e44b-4135-85db-2c75c4805c2e@infradead.org> (raw)
In-Reply-To: <23509de3-beab-4afd-b76f-4d675797e7d7@redhat.com>
On 2/3/24 23:21, Hans de Goede wrote:
> Hi Randy,
>
> On 2/4/24 02:26, Randy Dunlap wrote:
>> Hi ktr,
>>
>> Sorry for the late reply.
>>
>>
>> On 1/6/24 10:13, kernel test robot wrote:
>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>>> head: e2425464bc87159274879ab30f9d4fe624b9fcd2
>>> commit: f24945c77ed4c57b602632b9e3cbf5752e202a6f [12610/12662] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git
>>> reproduce: (https://download.01.org/0day-ci/archive/20240107/202401070202.BQvPxgyp-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/202401070202.BQvPxgyp-lkp@intel.com/
>>>
>>> All warnings (new ones prefixed by >>):
>>>
>>>>> Warning: file Documentation/ABI/testing/sysfs-platform-silicom#20:
>>>
>>
>> but what was the warning or problem here?
>> I don't see it.
>
> This has already been fixed by:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41237735ccde2cc3fe1d83ae0b776a085be6a22f
Hi Hans,
I was trying to understand the incomplete warning message...
Thanks.
--
#Randy
next prev parent reply other threads:[~2024-02-04 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 18:13 kernel test robot
2024-02-04 1:26 ` Randy Dunlap
2024-02-04 7:21 ` Hans de Goede
2024-02-04 15:40 ` Randy Dunlap [this message]
2024-02-05 5:11 ` Yujie Liu
2024-02-05 5:23 ` Randy Dunlap
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=7531b72b-e44b-4135-85db-2c75c4805c2e@infradead.org \
--to=rdunlap@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox