From: Kenny Cheng <chao.shun.cheng.tw@gmail.com>
To: viro@zeniv.linux.org.uk
Cc: c.s.cheng@realtek.com, cgroups@vger.kernel.org,
chao.shun.cheng.tw@gmail.com, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
muchun.song@linux.dev
Subject: Re: [PATCH] mm: avoid implicit type conversion
Date: Tue, 7 Jan 2025 13:48:17 +0800 [thread overview]
Message-ID: <20250107054817.3278424-1-chao.shun.cheng.tw@gmail.com> (raw)
In-Reply-To: <20250107040631.GN1977892@ZenIV>
> That makes no sense. Do you have bool (or _Bool) defined or typedefed
> to unsigned char somewhere? If so, that's the bug that needs to be
> fixed.
Yes, you're right!
It has defined in the other header file which is the root cause of
compiled error.
This patch can be ignored, thank you.
prev parent reply other threads:[~2025-01-07 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 3:51 Kenny Cheng
2025-01-07 4:06 ` Al Viro
2025-01-07 5:48 ` Kenny Cheng [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=20250107054817.3278424-1-chao.shun.cheng.tw@gmail.com \
--to=chao.shun.cheng.tw@gmail.com \
--cc=c.s.cheng@realtek.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--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