From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dhowells@redhat.com, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH] proc: Make inline name size calculation automatic
Date: Tue, 19 Jun 2018 09:01:01 +0100 [thread overview]
Message-ID: <20014.1529395261@warthog.procyon.org.uk> (raw)
In-Reply-To: <20180618174210.b8348d35bce35b2277cab660@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> wrote:
> Please cc Alexey on /proc patches.
If Alexey is responsible for procfs he should declare this in MAINTAINERS.
> What are the user-visible runtime effects of this change?
Memory usage only.
David
next prev parent reply other threads:[~2018-06-19 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 18:43 [PATCH] proc: Make inline name size calculation automatic David Howells
2018-06-19 0:42 ` Andrew Morton
2018-06-19 8:01 ` David Howells [this message]
2018-06-19 21:59 ` Andrew Morton
2018-06-14 20:09 Alexey Dobriyan
2018-06-14 20:30 ` David Howells
2018-06-15 17:15 ` Alexey Dobriyan
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=20014.1529395261@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).