From: Bert Karwatzki <spasswolf@web.de>
To: sashiko-reviews@lists.linux.dev
Cc: mkoutny@suse.com, tj@kernel.org, hannes@cmpxchg.org,
spasswolf@web.de, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: memcontrol: fix compilation
Date: Mon, 07 Sep 2026 19:29:03 +0200 [thread overview]
Message-ID: <57252878c60f15fbcf9d3c8904cc690db0998272.camel@web.de> (raw)
In-Reply-To: <20260907141808.3F4581F00A3A@smtp.kernel.org>
Am Montag, dem 07.09.2026 um 14:18 +0000 schrieb sashiko-bot@kernel.org:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] Redundant include of <linux/irq_work.h>
> --
>
> commit e46ef07a908650625b6fdf687c2624752ae3ff9c
> Author: Bert Karwatzki <spasswolf@web.de>
>
> mm: memcontrol: fix compilation
>
> This commit attempts to fix a compilation issue by including
> <linux/irq_work.h> in mm/memcontrol.c.
>
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > index 307203301a2a5..4740f519883a3 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -72,6 +72,7 @@
> > #include "memcontrol-v1.h"
> >
> > #include <linux/uaccess.h>
> > +#include <linux/irq_work.h>
>
> [Severity: Low]
> Is this additional include necessary? I noticed that <linux/irq_work.h> is
> already unconditionally included slightly earlier in this same file:
>
> mm/memcontrol.c:
> #include <linux/kmemleak.h>
> #include <linux/irq_work.h>
> #include "internal.h"
Yes, the include is neccessary because irq_work.h is not already include
in next-20260904.
In next-20260907 it's not included, either, but it is no longer necessary,
as mm/memcontrol.c no longer use struct irq_work_queue.
Bert Karwatzki
prev parent reply other threads:[~2026-09-07 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 14:14 Bert Karwatzki
[not found] ` <20260907141808.3F4581F00A3A@smtp.kernel.org>
2026-09-07 17:29 ` Bert Karwatzki [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=57252878c60f15fbcf9d3c8904cc690db0998272.camel@web.de \
--to=spasswolf@web.de \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tj@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®