[<prev] [next>] [day] [month] [year] [list]
Message-ID: <f55d7d68-737b-48fb-1857-95e1504d9fe0@huawei.com>
Date: Sat, 4 Mar 2023 18:18:17 +0800
From: "guanjing (D)" <guanjing6@...wei.com>
To: <borrello@...g.uniroma1.it>
CC: <bristot@...hat.com>, <c.giuffrida@...nl>,
<dietmar.eggemann@....com>, <dmitry.adamushko@...il.com>,
<h.j.bos@...nl>, <jkl820.git@...il.com>, <juri.lelli@...hat.com>,
<mgorman@...e.de>, <mingo@...e.hu>, <mingo@...hat.com>,
<pauld@...hat.com>, <peterz@...radead.org>, <rostedt@...dmis.org>,
<vincent.guittot@...aro.org>, <vschneid@...hat.com>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] sched: pick_next_rt_entity(): check list_entry
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.
Powered by blists - more mailing lists