From: Daniel Phillips <phillips@arcor.de>
To: Benjamin LaHaise <bcrl@redhat.com>,
Peter Chubb <peter@chubb.wattle.id.au>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, Pavel Machek <pavel@suse.cz>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Large block device patch, part 1 of 9
Date: Thu, 5 Sep 2002 02:38:58 +0200 [thread overview]
Message-ID: <E17mkfj-000627-00@starship> (raw)
In-Reply-To: <20020904200424.O1394@redhat.com>
On Thursday 05 September 2002 02:04, Benjamin LaHaise wrote:
> On Thu, Sep 05, 2002 at 09:04:01AM +1000, Peter Chubb wrote:
> > Unfortunately, this doesn't really buy you much ---- standard C type
> > promotion rules mean that whatever (within reason) you pass to
> > llsect() will work without warning.
>
> Not if someone changes a variable to a pointer by accident without
> updating the printk. It does happen.
The thing is, I don't see why we should be building castles and cathedrals
around printk. Just cast to the wider value, if you get it wrong you have
lost exactly what? Are people feeding the output of dmesg into scripts
that their systems depend upon? If so, we need to let evolution do its
work.
If this had something to do with how the kernel worked, it might be worth
inventing a new feature.
--
Daniel
next prev parent reply other threads:[~2002-09-05 0:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <825516963@toto.iv>
[not found] ` <15734.37217.686498.162782@wombat.chubb.wattle.id.au>
2002-09-05 0:04 ` Benjamin LaHaise
2002-09-05 0:38 ` Daniel Phillips [this message]
2002-09-05 1:31 ` Benjamin LaHaise
2002-09-05 4:05 ` Daniel Phillips
[not found] <fa.l4d1mqv.1ghm1h2@ifi.uio.no>
[not found] ` <fa.j8nq6dv.14lihor@ifi.uio.no>
2002-12-03 8:45 ` Giacomo Catenazzi
2002-12-03 17:40 ` H. Peter Anvin
2002-12-03 17:48 ` Giacomo Catenazzi
[not found] <15732.34929.657481.777572@notabene.cse.unsw.edu.au.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.44.0209030900410.1997-100000@home.transmeta.com.suse.lists.linux.kernel>
2002-09-03 16:23 ` Andi Kleen
2002-09-03 8:19 ` Linus Torvalds
2002-09-03 16:43 ` Nikita Danilov
2002-09-03 8:45 ` Linus Torvalds
2002-12-03 0:06 ` H. Peter Anvin
2002-12-05 10:58 ` Pavel Machek
2002-12-05 21:15 ` H. Peter Anvin
2002-08-23 5:47 Peter Chubb
2002-08-23 7:07 ` Andreas Dilger
2002-08-27 15:23 ` Pavel Machek
2002-08-27 22:58 ` Benjamin LaHaise
2002-08-27 23:40 ` Peter Chubb
2002-09-03 10:01 ` Neil Brown
2002-09-03 16:04 ` Linus Torvalds
2002-09-03 16:21 ` Thunder from the hill
2002-09-03 23:06 ` Neil Brown
2002-12-03 0:03 ` H. Peter Anvin
2002-09-03 19:42 ` Daniel Phillips
2002-09-03 19:50 ` Benjamin LaHaise
2002-09-03 20:02 ` Daniel Phillips
2002-09-03 20:04 ` Benjamin LaHaise
2002-09-03 20:19 ` Daniel Phillips
2002-09-03 20:25 ` Daniel Phillips
2002-09-03 20:05 ` Thunder from the hill
2002-09-03 20:19 ` Daniel Phillips
2002-12-03 0:05 ` H. Peter Anvin
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=E17mkfj-000627-00@starship \
--to=phillips@arcor.de \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=pavel@suse.cz \
--cc=peter@chubb.wattle.id.au \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®