From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org, Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH 2.4.21-pre4|BK] remove /proc/meminfo:MemShared
Date: Wed, 19 Feb 2003 14:03:25 +0100 [thread overview]
Message-ID: <200302191402.09004.m.c.p@wolk-project.de> (raw)
In-Reply-To: <20030219130008.GD531@fs.tum.de>
On Wednesday 19 February 2003 14:00, Adrian Bunk wrote:
Hi Adrian,
> I don't think it's good to do this change in a stable kernel series. The
> entry doesn't do any harm and there might be programs that parse
> /proc/meminfo and expect MemShared to be present.
well, I am not aware of any program that needs MemShared.
This is also in my WOLK tree for a long time (even longer than it was in 2.5)
and no one out there complained about it yet :)
ciao, Marc
next prev parent reply other threads:[~2003-02-19 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 12:42 Marc-Christian Petersen
2003-02-19 13:00 ` Adrian Bunk
2003-02-19 13:03 ` Marc-Christian Petersen [this message]
2003-02-19 14:22 ` Alan Cox
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=200302191402.09004.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®