From: Shiju Jose <shiju.jose@huawei.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Tony Luck <tony.luck@intel.com>,
"Jonathan Cameron" <jonathan.cameron@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: RE: linux-next: build warning after merge of the edac tree
Date: Tue, 1 Apr 2025 12:02:35 +0000 [thread overview]
Message-ID: <b6862252ef2b476cb1c650d5abe7c04d@huawei.com> (raw)
In-Reply-To: <20250401104457.GBZ-vDqbrZVOlEzhgf@fat_crate.local>
>-----Original Message-----
>From: Borislav Petkov <bp@alien8.de>
>Sent: 01 April 2025 11:45
>To: Shiju Jose <shiju.jose@huawei.com>
>Cc: Stephen Rothwell <sfr@canb.auug.org.au>; Mauro Carvalho Chehab
><mchehab+samsung@kernel.org>; Tony Luck <tony.luck@intel.com>; Jonathan
>Cameron <jonathan.cameron@huawei.com>; Linux Kernel Mailing List <linux-
>kernel@vger.kernel.org>; Linux Next Mailing List <linux-next@vger.kernel.org>
>Subject: Re: linux-next: build warning after merge of the edac tree
>
>On Tue, Apr 01, 2025 at 03:39:41PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> On Fri, 28 Feb 2025 18:51:02 +1100 Stephen Rothwell <sfr@canb.auug.org.au>
>wrote:
>> >
>> > After merging the edac tree, today's linux-next build (htmldocs)
>> > produced this warning:
>> >
>> > Documentation/edac/index.rst: WARNING: document isn't included in
>> > any toctree
>> >
>> > Introduced by commit
>> >
>> > db99ea5f2c03 ("EDAC: Add support for EDAC device features
>> > control")
>>
>> I am still getting this warning, but that commit is now in Linus' tree
>> :-(
>
>Shiju,
>
>please send this:
>
>https://lore.kernel.org/r/af3e1e183b034ea89ed6582a5382e5c3@huawei.com
>
>as a proper patch.
Hi Boris,
Sure.
Please check the fix patch sent.
https://lore.kernel.org/linux-edac/20250401115823.573-1-shiju.jose@huawei.com/T/#u
>
>Thx.
>
>--
>Regards/Gruss,
> Boris.
>
>https://people.kernel.org/tglx/notes-about-netiquette
Thanks,
Shiju
prev parent reply other threads:[~2025-04-01 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 7:51 linux-next: build warning after merge of the edac tree Stephen Rothwell
2025-02-28 10:04 ` Shiju Jose
2025-02-28 10:35 ` Borislav Petkov
2025-02-28 14:44 ` Jonathan Corbet
2025-02-28 15:05 ` Borislav Petkov
2025-04-01 4:39 ` Stephen Rothwell
2025-04-01 10:44 ` Borislav Petkov
2025-04-01 12:02 ` Shiju Jose [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=b6862252ef2b476cb1c650d5abe7c04d@huawei.com \
--to=shiju.jose@huawei.com \
--cc=bp@alien8.de \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.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