From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Sidhartha Kumar <sidhartha.kumar@oracle.com>
Cc: linux-kernel@vger.kernel.org, maple-tree@lists.infradead.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org, willy@infradead.org,
quic_jjohnson@quicinc.com
Subject: Re: [PATCH] tools/testing/radix-tree: add missing MODULE_DESCRIPTION definition
Date: Fri, 21 Jun 2024 09:40:49 -0400 [thread overview]
Message-ID: <rs6fzee44ilw6rhq2wauqwxdgnkgy3wudgr5alf2fuolrjm55f@32sznnbteorf> (raw)
In-Reply-To: <20240617195221.106565-1-sidhartha.kumar@oracle.com>
* Sidhartha Kumar <sidhartha.kumar@oracle.com> [240617 15:52]:
> Userspace builds of the radix-tree testing suite fails because of commit
> test_maple_tree: add the missing MODULE_DESCRIPTION() macro. Add the
> proper defines to tools/testing/radix-tree/maple.c and
> tools/testing/radix-tree/xarray.c so MODULE_DESCRIPTION has a definition.
> This allows the build to succeed.
>
> Fixes: 9f8090e8c4d1 ("test_maple_tree: add the missing MODULE_DESCRIPTION() macro")
> Signed-off-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>
> ---
> tools/testing/radix-tree/maple.c | 1 +
> tools/testing/radix-tree/xarray.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/tools/testing/radix-tree/maple.c b/tools/testing/radix-tree/maple.c
> index 175bb3346181..11f1efdf83f9 100644
> --- a/tools/testing/radix-tree/maple.c
> +++ b/tools/testing/radix-tree/maple.c
> @@ -19,6 +19,7 @@
> #define module_init(x)
> #define module_exit(x)
> #define MODULE_AUTHOR(x)
> +#define MODULE_DESCRIPTION(X)
> #define MODULE_LICENSE(x)
> #define dump_stack() assert(0)
>
> diff --git a/tools/testing/radix-tree/xarray.c b/tools/testing/radix-tree/xarray.c
> index f20e12cbbfd4..d0e53bff1eb6 100644
> --- a/tools/testing/radix-tree/xarray.c
> +++ b/tools/testing/radix-tree/xarray.c
> @@ -10,6 +10,7 @@
> #define module_init(x)
> #define module_exit(x)
> #define MODULE_AUTHOR(x)
> +#define MODULE_DESCRIPTION(X)
> #define MODULE_LICENSE(x)
> #define dump_stack() assert(0)
>
> --
> 2.45.2
>
prev parent reply other threads:[~2024-06-21 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 19:52 Sidhartha Kumar
2024-06-21 13:40 ` Liam R. Howlett [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=rs6fzee44ilw6rhq2wauqwxdgnkgy3wudgr5alf2fuolrjm55f@32sznnbteorf \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=quic_jjohnson@quicinc.com \
--cc=sidhartha.kumar@oracle.com \
--cc=willy@infradead.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