From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
mathieu.desnoyers@efficios.com, rdunlap@infradead.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: build warnings after merge of Linus' tree
Date: Mon, 7 Apr 2025 15:17:01 +0530 [thread overview]
Message-ID: <e5df899e-4edf-41cc-8611-720a67b0a584@linux.ibm.com> (raw)
In-Reply-To: <9B0D38E4-3414-43B9-8F41-D552755DC81E@linux.ibm.com>
I think I have messed up. Please ignore below mail.
On 07/04/25 2:29 pm, Venkat wrote:
> On IBM Power9 only below warning is observed.
>
> WARNING: modpost: missing MODULE_DESCRIPTION() in lib/tests/slub_kunit.o
>
> I have tested the patch and the above reported warning is fixed. Please add below tag.
>
>
> Tested-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
>
> Regards,
> Venkat.
>
>
>
next prev parent reply other threads:[~2025-04-07 9:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 8:59 linux-next: build warnings after merge of Linus' tree Venkat
2025-04-07 9:47 ` Venkat Rao Bagalkote [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-13 1:55 Stephen Rothwell
2025-11-13 8:16 ` Mauro Carvalho Chehab
2025-11-13 16:23 ` Jonathan Corbet
2025-11-13 22:01 ` Mauro Carvalho Chehab
2025-11-13 22:28 ` Randy Dunlap
2025-11-13 22:42 ` Randy Dunlap
2025-11-13 8:49 ` Michael S. Tsirkin
2025-11-13 10:32 ` Mauro Carvalho Chehab
2025-04-06 22:48 Stephen Rothwell
2023-05-08 4:49 Stephen Rothwell
2023-05-08 4:52 ` Randy Dunlap
2023-05-08 4:53 ` Randy Dunlap
2023-05-08 7:50 ` Peter Zijlstra
2021-03-29 9:04 Stephen Rothwell
2021-04-21 6:23 ` Stephen Rothwell
2021-04-21 13:06 ` Rob Herring
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=e5df899e-4edf-41cc-8611-720a67b0a584@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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