From: huzijun <zijun_hu@icloud.com>
To: Breno Leitao <leitao@debian.org>
Cc: Joel Becker <jlbec@evilplan.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org, Zijun Hu <quic_zijuhu@quicinc.com>
Subject: Re: [PATCH v2 1/3] configfs: Delete semicolon from macro type_print() definition
Date: Thu, 17 Apr 2025 23:11:10 +0800 [thread overview]
Message-ID: <CDCE55D6-2296-4B36-9A65-369EC13492DC@icloud.com> (raw)
In-Reply-To: <aAEXAL3ypUn4G/oe@gmail.com>
> 在 2025年4月17日,22:58,Breno Leitao <leitao@debian.org> 写道:
>
> On Tue, Apr 15, 2025 at 08:34:25PM +0800, Zijun Hu wrote:
>> From: Zijun Hu <quic_zijuhu@quicinc.com>
>>
>> Macro type_print() definition ends with semicolon, so will cause
>> the subsequent macro invocations end with two semicolons.
>>
>> Fix by deleting the semicolon from the macro definition.
>>
>> Reviewed-by: Joel Becker <jlbec@evilplan.org>
>> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
>> ---
>> fs/configfs/dir.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/configfs/dir.c b/fs/configfs/dir.c
>> index 7d10278db30d667d0ef7e1140e54961c5a440c41..0a011bdad98c492227859ff328d61aeed2071e24 100644
>> --- a/fs/configfs/dir.c
>> +++ b/fs/configfs/dir.c
>> @@ -970,7 +970,7 @@ static void configfs_dump_one(struct configfs_dirent *sd, int level)
>> {
>> pr_info("%*s\"%s\":\n", level, " ", configfs_get_name(sd));
>>
>> -#define type_print(_type) if (sd->s_type & _type) pr_info("%*s %s\n", level, " ", #_type);
>> +#define type_print(_type) if (sd->s_type & _type) pr_info("%*s %s\n", level, " ", #_type)
>> type_print(CONFIGFS_ROOT);
>> type_print(CONFIGFS_DIR);
>> type_print(CONFIGFS_ITEM_ATTR);
>
> As I've asked in V1. Is this macro being used?
>
yes. it is being used by those 3 statements which follows the macro definition (^^)
> --breno
next prev parent reply other threads:[~2025-04-17 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 12:34 [PATCH v2 0/3] configfs: fix bugs Zijun Hu
2025-04-15 12:34 ` [PATCH v2 1/3] configfs: Delete semicolon from macro type_print() definition Zijun Hu
2025-04-17 14:58 ` Breno Leitao
2025-04-17 15:11 ` huzijun [this message]
2025-04-15 12:34 ` [PATCH v2 2/3] configfs: Do not override creating attribute file failure in populate_attrs() Zijun Hu
2025-04-17 14:57 ` Breno Leitao
2025-04-15 12:34 ` [PATCH v2 3/3] configfs: Correct error value returned by API config_item_set_name() Zijun Hu
2025-04-17 14:49 ` Breno Leitao
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=CDCE55D6-2296-4B36-9A65-369EC13492DC@icloud.com \
--to=zijun_hu@icloud.com \
--cc=jlbec@evilplan.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=quic_zijuhu@quicinc.com \
--cc=viro@zeniv.linux.org.uk \
/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®