[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51A2BAE9.40307@jp.fujitsu.com>
Date: Mon, 27 May 2013 10:46:17 +0900
From: HATAYAMA Daisuke <d.hatayama@...fujitsu.com>
To: Zhang Yanfei <zhangyanfei.yes@...il.com>
CC: "Eric W. Biederman" <ebiederm@...ssion.com>,
Vivek Goyal <vgoyal@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
Simon Horman <horms@...ge.net.au>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/7] Documentation/devices.txt: Mark /dev/oldmem obsolete
(2013/05/26 15:36), Zhang Yanfei wrote:
> From: Zhang Yanfei <zhangyanfei@...fujitsu.com>
>
> Signed-off-by: Zhang Yanfei <zhangyanfei@...fujitsu.com>
> Cc: Dave Jones <davej@...hat.com>
> ---
> Documentation/devices.txt | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devices.txt b/Documentation/devices.txt
> index 08f01e7..c8e4002 100644
> --- a/Documentation/devices.txt
> +++ b/Documentation/devices.txt
> @@ -100,8 +100,7 @@ Your cooperation is appreciated.
> 10 = /dev/aio Asynchronous I/O notification interface
> 11 = /dev/kmsg Writes to this come out as printk's, reads
> export the buffered printk records.
> - 12 = /dev/oldmem Used by crashdump kernels to access
> - the memory of the kernel that crashed.
> + 12 = /dev/oldmem OBSOLETE
>
> 1 block RAM disk
> 0 = /dev/ram0 First RAM disk
>
This is the new patch. Looking at other parts of devices.txt, obsolete is
sometimes used together with unused. I guess obsolete means this is old interface so
don't use it as much as possible and unused means this is not used at all now.
You remove old memory interface completely in this patch set, so is it better to add
unused, too?
--
Thanks.
HATAYAMA, Daisuke
--
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