From: "H. Peter Anvin" <hpa@zytor.com>
To: Rob Landley <rob@landley.net>
Cc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Simon Horman <horms@verge.net.au>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vivek Goyal <vgoyal@redhat.com>,
Zhang Yanfei <zhangyanfei.yes@gmail.com>
Subject: Re: [PATCH v2 2/7] Documentation/devices.txt: Mark /dev/oldmem obsolete
Date: Tue, 28 May 2013 10:35:23 -0700 [thread overview]
Message-ID: <51A4EADB.9080703@zytor.com> (raw)
In-Reply-To: <1369761966.2776.39@driftwood>
On 05/28/2013 10:26 AM, Rob Landley wrote:
>>
>> So, could I just use UNSED to replace OBSOLETE here? Or use
>> "OBSOLETE/UNUSED"?
>
> Obsolete is fine.
>
> Obsolete means it was used at some point, and thus reusing it might
> confuse or conflcit with legacy software. Unused could just mean that we
> left a gap for some reason, it doesn't imply it ever was used.
>
> Explicitly documenting "unused" is kind of silly: all the ones we
> _don't_ document are presumably unused. Obsolete carries with it a very
> mild warning about legacy software, which is presumably why we still
> bother to mention it at all instead of just removing the entry.
>
> (Then again the point was that nothing ever used this interface in the
> first place. Personally I'd just have removed the entry...)
>
"Obsolete" in this specific context means that the reservation is
obsolete, but was used in kernels past, therefore the name and number
should not be reused to prevent old software from misbehaving.
-hpa
next prev parent reply other threads:[~2013-05-28 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 6:31 [PATCH v2 0/7] Remove unused /dev/oldmem interface Zhang Yanfei
2013-05-26 6:34 ` [PATCH v2 1/7] /dev/oldmem: Remove the interface Zhang Yanfei
2013-05-26 6:36 ` [PATCH v2 2/7] Documentation/devices.txt: Mark /dev/oldmem obsolete Zhang Yanfei
2013-05-27 1:46 ` HATAYAMA Daisuke
2013-05-27 1:54 ` Zhang Yanfei
2013-05-27 2:16 ` HATAYAMA Daisuke
2013-05-28 6:17 ` Rob Landley
2013-05-28 6:25 ` Zhang Yanfei
2013-05-28 17:26 ` Rob Landley
2013-05-28 17:35 ` H. Peter Anvin [this message]
2013-05-28 22:29 ` Eric W. Biederman
2013-05-29 7:45 ` Zhang Yanfei
2013-05-26 6:38 ` [PATCH v2 3/7] Documentation/kdump/kdump.txt: Remove /dev/oldmem description Zhang Yanfei
2013-05-26 6:40 ` [PATCH v2 4/7] mips: Remove savemaxmem parameter setup Zhang Yanfei
2013-05-26 6:42 ` [PATCH v2 5/7] powerpc: " Zhang Yanfei
2013-05-26 6:44 ` [PATCH v2 6/7] ia64: Remove setting for saved_max_pfn Zhang Yanfei
2013-05-26 6:45 ` [PATCH v2 7/7] s390: " Zhang Yanfei
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=51A4EADB.9080703@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=vgoyal@redhat.com \
--cc=zhangyanfei.yes@gmail.com \
--cc=zhangyanfei@cn.fujitsu.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