From: Tejun Heo <tj@kernel.org>
To: Maxime Ripard <mripard@kernel.org>
Cc: Waiman Long <llong@redhat.com>,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
hannes@cmpxchg.org, mkoutny@suse.com, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH -next] kernel/cgroup: Remove the unused variable climit
Date: Tue, 14 Jan 2025 10:44:29 -1000 [thread overview]
Message-ID: <Z4bMrXdcNWEj9MYc@slm.duckdns.org> (raw)
In-Reply-To: <20250114-voracious-optimal-alligator-cdaaba@houat>
On Tue, Jan 14, 2025 at 06:56:38PM +0100, Maxime Ripard wrote:
> On Tue, Jan 14, 2025 at 10:41:28AM -0500, Waiman Long wrote:
> > On 1/14/25 1:28 AM, Jiapeng Chong wrote:
> > > Variable climit is not effectively used, so delete it.
> > >
> > > kernel/cgroup/dmem.c:302:23: warning: variable ‘climit’ set but not used.
> > >
> > > Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> > > Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=13512
> > > Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> > > ---
> > > kernel/cgroup/dmem.c | 3 +--
> > > 1 file changed, 1 insertion(+), 2 deletions(-)
> > >
> > > diff --git a/kernel/cgroup/dmem.c b/kernel/cgroup/dmem.c
> > > index 52736ef0ccf2..78d9361ed521 100644
> > > --- a/kernel/cgroup/dmem.c
> > > +++ b/kernel/cgroup/dmem.c
> > > @@ -299,7 +299,7 @@ bool dmem_cgroup_state_evict_valuable(struct dmem_cgroup_pool_state *limit_pool,
> > > bool ignore_low, bool *ret_hit_low)
> > > {
> > > struct dmem_cgroup_pool_state *pool = test_pool;
> > > - struct page_counter *climit, *ctest;
> > > + struct page_counter *ctest;
> > > u64 used, min, low;
> > > /* Can always evict from current pool, despite limits */
> > > @@ -324,7 +324,6 @@ bool dmem_cgroup_state_evict_valuable(struct dmem_cgroup_pool_state *limit_pool,
> > > {}
> > > }
> > > - climit = &limit_pool->cnt;
> > > ctest = &test_pool->cnt;
> > > dmem_cgroup_calculate_protection(limit_pool, test_pool);
> >
> > The dmem controller is actually pulled into the drm tree at the moment.
> >
> > cc relevant parties on how to handle this fix commit.
>
> We can either take it through drm with one of the cgroup maintainers
> ack, or they can merge the PR in their tree and merge the fixes as they
> wish through their tree.
Acked-by: Tejun Heo <tj@kernel.org>
Please route with the rest of dmem changes.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-01-14 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 6:28 Jiapeng Chong
2025-01-14 15:41 ` Waiman Long
2025-01-14 17:56 ` Maxime Ripard
2025-01-14 20:44 ` Tejun Heo [this message]
2025-01-15 8:50 ` Maxime Ripard
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=Z4bMrXdcNWEj9MYc@slm.duckdns.org \
--to=tj@kernel.org \
--cc=abaci@linux.alibaba.com \
--cc=cgroups@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hannes@cmpxchg.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llong@redhat.com \
--cc=mkoutny@suse.com \
--cc=mripard@kernel.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
all inboxes | Powered by JetHome®