From: Michael Rothwell <rothwell@holly-springs.nc.us>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Weinehall <tao@acc.umu.se>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.18pre20
Date: Tue, 07 Nov 2000 21:15:53 -0500 [thread overview]
Message-ID: <3A08B759.1C36A9C0@holly-springs.nc.us> (raw)
In-Reply-To: <E13tKjj-00085w-00@the-village.bc.nu>
Alan Cox wrote:
>
> > On Tue, Nov 07, 2000 at 09:02:36PM -0500, Michael Rothwell wrote:
> > > 64-bit printk.
> >
> > Please consider this one Alan, if not for v2.2.18, then at least for
> > v2.2.19pre1.
>
> Nobody has explained why we even need it.
Alan Cox wrote:
>
> Why do we need it ?
To print 64-bit debugging output on 32-bit machines. I personally need
it to aid with development of a 64-bit filesystem. We're maintaining our
own 2.2.17 patched kernel here, but I figure that other people can make
use of 64-bit printk in their efforts as well.
Perhaps a better question would be, why reject it? 2.4 supports 64-bit
printk, right? It would be nice to have it on 2.2 as well, as it may be
a while before 2.4 is widely used in production machines.
-M
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-08 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 1:59 Alan Cox
2000-11-08 2:02 ` Michael Rothwell
2000-11-08 2:06 ` David Weinehall
2000-11-08 2:13 ` Alan Cox
2000-11-08 2:15 ` Michael Rothwell [this message]
2000-11-08 19:16 ` Michael Rothwell
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=3A08B759.1C36A9C0@holly-springs.nc.us \
--to=rothwell@holly-springs.nc.us \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tao@acc.umu.se \
/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
all inboxes | Powered by JetHome®