(2013/05/27 10:54), Zhang Yanfei wrote: > ? 2013?05?27? 09:46, HATAYAMA Daisuke ??: >> (2013/05/26 15:36), Zhang Yanfei wrote: >>> From: Zhang Yanfei <zhangyanfei at cn.fujitsu.com> >>> >>> Signed-off-by: Zhang Yanfei <zhangyanfei at cn.fujitsu.com> >>> Cc: Dave Jones <davej at redhat.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? >> > > Does obsolete also mean "not used anymore"? I don't know. I think we can wait for some native > English speakers to comment on this. > Yes. To be honest, I'm still suspecting "unused" doesn't include meaning of "removed"... -- Thanks. HATAYAMA, Daisuke