[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130529152007.893940a04d95fa1e38e851d4@linux-foundation.org>
Date: Wed, 29 May 2013 15:20:07 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Zhang Yanfei <zhangyanfei@...fujitsu.com>
Cc: HATAYAMA Daisuke <d.hatayama@...fujitsu.com>,
Zhang Yanfei <zhangyanfei.yes@...il.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Simon Horman <horms@...ge.net.au>,
"H. Peter Anvin" <hpa@...or.com>, davej@...hat.com,
Vivek Goyal <vgoyal@...hat.com>
Subject: Re: [PATCH 2/7] Documentation/devices.txt: Remove /dev/oldmem
description
On Mon, 27 May 2013 09:27:42 +0800 Zhang Yanfei <zhangyanfei@...fujitsu.com> wrote:
> ___ 2013___05___27___ 09:27, HATAYAMA Daisuke ______:
> > (2013/05/26 9:58), Zhang Yanfei wrote:
> >> ___ 2013___05___26___ 07:20, Eric W. Biederman ______:
> >>> Zhang Yanfei <zhangyanfei.yes@...il.com> writes:
> >>>
> >>>> From: Zhang Yanfei <zhangyanfei@...fujitsu.com>
> >>>
> >>> Won't we want to keep this reservation around to so that this number
> >>> doesn't get reused, and cause people confusion when
> >>> upgrading/downgrading kernels?
> >>
> >> Ah, yes. I will just keep this and add a note to make people know that
> >> it is removed in the next version.
> >>
> >
> > It looks enough writing "obsolete" according to the other parts of the same file.
> >
>
> I've sent the v2 version and actually did what you said.
I can't find any v2 version of this patchset.
I did this:
--- a/Documentation/devices.txt~dev-oldmem-remove-the-interface-fix
+++ a/Documentation/devices.txt
@@ -102,6 +102,7 @@ Your cooperation is appreciated.
export the buffered printk records.
12 = /dev/oldmem Used by crashdump kernels to access
the memory of the kernel that crashed.
+ (obsolete)
1 block RAM disk
0 = /dev/ram0 First RAM disk
_
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists