From: "guanjing (D)" <guanjing6@huawei.com>
To: <borrello@diag.uniroma1.it>
Cc: <bristot@redhat.com>, <c.giuffrida@vu.nl>,
<dietmar.eggemann@arm.com>, <dmitry.adamushko@gmail.com>,
<h.j.bos@vu.nl>, <jkl820.git@gmail.com>, <juri.lelli@redhat.com>,
<mgorman@suse.de>, <mingo@elte.hu>, <mingo@redhat.com>,
<pauld@redhat.com>, <peterz@infradead.org>, <rostedt@goodmis.org>,
<vincent.guittot@linaro.org>, <vschneid@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] sched: pick_next_rt_entity(): check list_entry
Date: Sat, 4 Mar 2023 18:18:17 +0800 [thread overview]
Message-ID: <f55d7d68-737b-48fb-1857-95e1504d9fe0@huawei.com> (raw)
In-Reply-To: <d3af2533-2990-e884-eb9a-20cbbfedde23@huawei.com>
Hi, borrello:
I wonder why you send this patch? Did you meet such a problem in a
real-world scenario, or it is a static warning style?
Thanks,
Guanjin.
next parent reply other threads:[~2023-03-04 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8f5c938f-5c31-655b-fd8d-415fa192d705@huawei.com>
[not found] ` <d3af2533-2990-e884-eb9a-20cbbfedde23@huawei.com>
2023-03-04 10:18 ` guanjing (D) [this message]
2023-02-06 22:33 Pietro Borrello
2023-02-07 12:29 ` Phil Auld
2023-02-07 15:11 ` Steven Rostedt
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=f55d7d68-737b-48fb-1857-95e1504d9fe0@huawei.com \
--to=guanjing6@huawei.com \
--cc=20230128-list-entry-null-check-sched-v3-1-b1a71bd1ac6b@diag.uniroma1.it \
--cc=borrello@diag.uniroma1.it \
--cc=bristot@redhat.com \
--cc=c.giuffrida@vu.nl \
--cc=dietmar.eggemann@arm.com \
--cc=dmitry.adamushko@gmail.com \
--cc=h.j.bos@vu.nl \
--cc=jkl820.git@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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®