From: David Rientjes <rientjes@google.com>
To: Florian Westphal <fw@strlen.de>
Cc: linux-mm@kvack.org, cl@linux.com, penberg@kernel.org,
iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: remove __krealloc
Date: Thu, 12 Dec 2019 15:00:03 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.1912121459400.121505@chino.kir.corp.google.com> (raw)
In-Reply-To: <20191212223442.22141-1-fw@strlen.de>
On Thu, 12 Dec 2019, Florian Westphal wrote:
> Since 5.5-rc1 the last user of this function is gone, so remove the
> functionality.
>
> See commit
> 2ad9d7747c10 ("netfilter: conntrack: free extension area immediately")
> for details.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
So this also means that we can fold __do_krealloc() into krealloc()?
next prev parent reply other threads:[~2019-12-12 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 22:34 Florian Westphal
2019-12-12 23:00 ` David Rientjes [this message]
2019-12-12 23:18 ` Florian Westphal
2019-12-13 18:59 ` David Rientjes
2019-12-13 10:17 ` David Hildenbrand
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=alpine.DEB.2.21.1912121459400.121505@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=fw@strlen.de \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@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