From: Matthew Wilcox <willy@infradead.org>
To: Pintu Kumar <pintu@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, iamjoonsoo.kim@lge.com,
rientjes@google.com, penberg@kernel.org, cl@linux.com,
pintu.ping@gmail.com
Subject: Re: [PATCH] mm/slab.h: Fix duplicate include file kmemleak.h
Date: Thu, 10 Sep 2020 17:15:47 +0100 [thread overview]
Message-ID: <20200910161547.GT6583@casper.infradead.org> (raw)
In-Reply-To: <0101017478cb7f12-16ae9fdb-ef30-4277-ab57-e31e12598466-000000@us-west-2.amazonses.com>
On Thu, Sep 10, 2020 at 04:13:56PM +0000, Pintu Kumar wrote:
> As I was browsing through this code, I found that linux/kmemleak.h
> was declared twice.
>
> When I run ./scripts/checkincludes.pl it reported the same:
> mm/slab.h: linux/kmemleak.h is included more than once.
Already reported yesterday and also on August 18th.
prev parent reply other threads:[~2020-09-10 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 16:13 [PATCH] mm/slab.h: Fix duplicate include file kmemleak.h Pintu Kumar
2020-09-10 16:15 ` Matthew Wilcox [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=20200910161547.GT6583@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=pintu.ping@gmail.com \
--cc=pintu@codeaurora.org \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).