From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
loongson-kernel@lists.loongnix.cn
Subject: [PATCH 0/2] module: Do some small changes
Date: Fri, 16 Jun 2023 09:51:31 +0800 [thread overview]
Message-ID: <1686880293-29594-1-git-send-email-yangtiezhu@loongson.cn> (raw)
The first patch is suggested by Xi Zhang <zhangxi@kylinos.cn> offline,
the second patch is inspired by the first patch, no functional changes.
Tiezhu Yang (2):
module: Make is_mapping_symbol() return bool
module: Make is_valid_name() return bool
include/linux/module_symbol.h | 2 +-
scripts/mod/modpost.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.1.0
next reply other threads:[~2023-06-16 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 1:51 Tiezhu Yang [this message]
2023-06-16 1:51 ` [PATCH 1/2] module: Make is_mapping_symbol() return bool Tiezhu Yang
2023-06-16 1:51 ` [PATCH 2/2] module: Make is_valid_name() " Tiezhu Yang
2023-09-21 0:10 ` [PATCH 0/2] module: Do some small changes Luis Chamberlain
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=1686880293-29594-1-git-send-email-yangtiezhu@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=mcgrof@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).