From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<patches@lists.linux.dev>
Subject: Re: [PATCH 4/4] clk: Make debugfs code into a loadable kernel module
Date: Wed, 22 Jan 2025 15:29:28 -0800 [thread overview]
Message-ID: <99de1bb7-0a6b-4965-b913-e0ec6e428477@quicinc.com> (raw)
In-Reply-To: <20250108005854.2973184-5-sboyd@kernel.org>
On 1/7/25 16:58, Stephen Boyd wrote:
> Split the debugfs code for the clk framework into a separate loadable
> kernel module. This allows the debugfs code to be loaded later, or not
> at all.
>
> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
...
> +MODULE_LICENSE("GPL");
Since commit 1fffe7a34c89 ("script: modpost: emit a warning when the
description is missing"), a module without a MODULE_DESCRIPTION() will
result in a warning with make W=1. Please add a MODULE_DESCRIPTION()
to avoid this warning.
prev parent reply other threads:[~2025-01-22 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 0:58 [PATCH 0/4] clk: Move debugfs to " Stephen Boyd
2025-01-08 0:58 ` [PATCH 1/4] clk: Prepare clk_debug_create_one() to be split off Stephen Boyd
2025-01-08 0:58 ` [PATCH 2/4] clk: Use struct clk_hw instead of struct clk_core for debugfs Stephen Boyd
2025-01-08 0:58 ` [PATCH 3/4] clk: Iterate instead of recurse for debugfs printing Stephen Boyd
2025-01-08 0:58 ` [PATCH 4/4] clk: Make debugfs code into a loadable kernel module Stephen Boyd
2025-01-10 6:45 ` kernel test robot
2025-01-11 11:51 ` kernel test robot
2025-01-22 23:29 ` Jeff Johnson [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=99de1bb7-0a6b-4965-b913-e0ec6e428477@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=patches@lists.linux.dev \
--cc=sboyd@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®