From: zhang warden <zhangwarden@gmail.com>
To: Shresth Prasad <shresthprasad7@gmail.com>
Cc: Marcos Paulo de Souza <mpdesouza@suse.com>,
jikos@kernel.org, joe.lawrence@redhat.com, jpoimboe@kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
live-patching@vger.kernel.org, mbenes@suse.cz, pmladek@suse.com,
shuah@kernel.org, skhan@linuxfoundation.org
Subject: Re: [PATCH] Fix implicit cast warning in test_klp_state.c
Date: Wed, 21 Feb 2024 10:38:56 +0800 [thread overview]
Message-ID: <B052E4A4-3652-452F-B4F9-F36860143CC3@gmail.com> (raw)
In-Reply-To: <6fcd7da4-f7c1-4f2c-9214-70ec77443572@gmail.com>
Would you please pasting the original warning of your complier?
And did you check your source code if your source code is the the latest version?
Regards,
Warden
> On Feb 20, 2024, at 21:20, Shresth Prasad <shresthprasad7@gmail.com> wrote:
>
>> What compiler version and architecture? Are you >compiling using flags like W=1?
>> I would advise you to always add more information >about how the problem
>> manifests, and what you are executing. This can >help to nail down the issue quicker.
>
> I'll keep that in mind. I'm on an x86_64 system with gcc version 13.2.1 20230801.
>
> I'm using the command `make -j15 -C tools/testing/selftests` with no additional flags.
>
> Regards,
> Shresth
next prev parent reply other threads:[~2024-02-21 2:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 22:51 [PATCH] Fix implicit cast warning in test_klp_state.c Shresth Prasad
2024-02-19 14:16 ` Marcos Paulo de Souza
2024-02-20 6:06 ` zhang warden
2024-02-20 11:53 ` Shresth Prasad
2024-02-20 12:00 ` Marcos Paulo de Souza
2024-02-20 13:20 ` Shresth Prasad
2024-02-21 2:38 ` zhang warden [this message]
2024-02-21 9:59 ` Shresth Prasad
2024-02-21 12:44 ` Nicolai Stange
2024-02-22 8:12 ` Shresth Prasad
[not found] ` <22981.124022107441100115@us-mta-655.us.mimecast.lan>
2024-02-21 18:26 ` Joe Lawrence
2024-02-22 8:35 ` Shresth Prasad
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=B052E4A4-3652-452F-B4F9-F36860143CC3@gmail.com \
--to=zhangwarden@gmail.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpdesouza@suse.com \
--cc=pmladek@suse.com \
--cc=shresthprasad7@gmail.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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 NNTP newsgroup(s).