From: Andrew Morton <akpm@linux-foundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Zhang Yanfei <zhangyanfei.yes@gmail.com>,
Simon Horman <horms@verge.net.au>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] Remove unused /dev/oldmem interface
Date: Wed, 29 May 2013 15:11:59 -0700 [thread overview]
Message-ID: <20130529151159.2f1d6b5092c58b61724bee7c@linux-foundation.org> (raw)
In-Reply-To: <51A4C926.2040701@zytor.com>
On Tue, 28 May 2013 08:11:34 -0700 "H. Peter Anvin" <hpa@zytor.com> wrote:
> On 05/28/2013 07:37 AM, Vivek Goyal wrote:
> >
> > Eric,
> >
> > Should we schedule the removal of this interface after 1-2 releases
> > and give a warning once if anybody opens /dev/oldmem and tell them
> > to use /proc/vmcore instead?
> >
> > I am kind of inclined towards warning approarch. If there is any xyz
> > /dev/oldmem user in the wild out there, he/she atleast gets a chance to
> > migrate to /proc/vmcore.
> >
>
> This has been discussed ad nauseam at the Kernel Summit. It doesn't work.
>
Who said that and what was their evidence? Giving users (especially
the more technical ones) several months warning is eminently sensible.
Although it doesn't appear to be necessary in this case.
next prev parent reply other threads:[~2013-05-29 22:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 3:21 Zhang Yanfei
2013-05-25 3:24 ` [PATCH 1/7] /dev/oldmem: Remove the interface Zhang Yanfei
2013-05-25 3:26 ` [PATCH 2/7] Documentation/devices.txt: Remove /dev/oldmem description Zhang Yanfei
2013-05-25 23:20 ` Eric W. Biederman
2013-05-26 0:58 ` Zhang Yanfei
2013-05-27 1:27 ` HATAYAMA Daisuke
2013-05-27 1:27 ` Zhang Yanfei
2013-05-29 22:20 ` Andrew Morton
2013-05-30 5:49 ` Zhang Yanfei
2013-05-25 3:27 ` [PATCH 3/7] Documentation/kdump/kdump.txt: " Zhang Yanfei
2013-05-25 3:29 ` [PATCH 4/7] mips: Remove savemaxmem parameter setup Zhang Yanfei
2013-05-25 3:31 ` [PATCH 5/7] powerpc: " Zhang Yanfei
2013-05-25 3:33 ` [PATCH 6/7] ia64: Remove setting for saved_max_pfn Zhang Yanfei
2013-05-25 3:36 ` [PATCH 7/7] s390: " Zhang Yanfei
2013-05-25 7:11 ` [PATCH 0/7] Remove unused /dev/oldmem interface H. Peter Anvin
2013-05-25 23:25 ` Eric W. Biederman
2013-05-28 14:37 ` Vivek Goyal
2013-05-28 15:11 ` H. Peter Anvin
2013-05-29 22:11 ` Andrew Morton [this message]
2013-05-28 19:00 ` Eric W. Biederman
2013-05-29 16:10 ` Vivek Goyal
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=20130529151159.2f1d6b5092c58b61724bee7c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
--cc=zhangyanfei.yes@gmail.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
all inboxes | Powered by JetHome®