From: "H. Peter Anvin" <hpa@zytor.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jacques Gelinas <jacques@solucorp.qc.ca>,
Matija Nalis <mnalis@jagor.srce.hr>,
Matija Nalis <mnalis@voyager.hr>,
trivial@kernel.org
Subject: Re: [PATCH] Remove a few UMSDOS leftovers
Date: Thu, 24 May 2007 16:24:10 -0700 [thread overview]
Message-ID: <46561E9A.7020402@zytor.com> (raw)
In-Reply-To: <200705250115.04491.jesper.juhl@gmail.com>
Jesper Juhl wrote:
> Ok, that makes sense. How about this version :
Could you document which numbers were actually used by umsdos, instead
of reserving a full block of 256? Since it's dead, it's not going to
eat any more numbers.
-hpa
next prev parent reply other threads:[~2007-05-24 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 22:58 [PATCH] Remove a few UMSDOS leftovers Jesper Juhl
2007-05-24 23:07 ` H. Peter Anvin
2007-05-24 23:15 ` Jesper Juhl
2007-05-24 23:24 ` H. Peter Anvin [this message]
2007-05-24 23:27 ` Jesper Juhl
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=46561E9A.7020402@zytor.com \
--to=hpa@zytor.com \
--cc=jacques@solucorp.qc.ca \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mnalis@jagor.srce.hr \
--cc=mnalis@voyager.hr \
--cc=trivial@kernel.org \
/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