From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: kyle@infradead.org, linux-parisc@vger.kernel.org
Subject: Re: resource_size_t printk woes...
Date: Thu, 01 Jan 2009 18:32:16 +0100 [thread overview]
Message-ID: <495CFE20.2000702@gmx.de> (raw)
In-Reply-To: <20090101171442.5BF174EDA@hiauly1.hia.nrc.ca>
John David Anglin wrote:
> Hi Helge,
>
> I just want to say that I like Kyle's approach. There already exists
> the 'R' modifier for %p. This outputs a pair of resource_size_t values.
> We just need a modifier to handle the printing of the start value in
> a manner similar to that for the 'R' modifier. So, I think this issue
> needs another go around.
Sadly none of the approaches is really nice, as with Kyle's approach we'd
loose the type-checking of printk.
But yes, maybe that's the best choice of all bad ones.
Will you try/come up with a patch to vsprintf.c?
Helge
next prev parent reply other threads:[~2009-01-01 17:32 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 20:04 2.6.28-rcX in pretty bad shape on parisc Helge Deller
2008-11-19 1:33 ` Thibaut VARENE
2008-11-19 15:47 ` Helge Deller
2008-11-19 2:31 ` James Bottomley
2008-11-19 9:13 ` Domenico Andreoli
2008-11-19 14:20 ` James Bottomley
2008-11-19 15:12 ` John David Anglin
2008-11-19 16:25 ` Helge Deller
2008-11-19 18:13 ` Helge Deller
2008-11-20 7:55 ` Helge Deller
2008-11-20 12:57 ` Thibaut VARENE
2008-11-20 15:14 ` John David Anglin
2008-11-20 3:51 ` John David Anglin
2008-11-20 16:57 ` John David Anglin
2008-11-22 5:57 ` Grant Grundler
2008-11-22 6:14 ` Grant Grundler
2008-11-22 19:48 ` John David Anglin
2008-11-22 21:37 ` John David Anglin
2008-11-22 23:01 ` James Bottomley
2008-11-23 16:54 ` John David Anglin
2008-11-22 6:11 ` Grant Grundler
2008-11-23 7:13 ` Grant Grundler
2008-11-23 16:36 ` John David Anglin
2008-11-23 16:57 ` John David Anglin
2008-11-25 2:54 ` John David Anglin
2008-11-25 13:33 ` Carlos O'Donell
2008-11-25 13:58 ` Guy Martin
2008-11-25 14:07 ` Carlos O'Donell
2008-11-26 17:51 ` Guy Martin
2008-11-30 20:24 ` John David Anglin
2008-11-30 21:03 ` Helge Deller
2008-12-02 0:00 ` John David Anglin
2008-12-01 10:54 ` Thibaut VARENE
2008-12-03 20:41 ` Helge Deller
2008-12-08 5:15 ` Kyle McMartin
2008-12-08 15:23 ` John David Anglin
2008-12-08 15:34 ` Kyle McMartin
2008-12-08 15:57 ` John David Anglin
2008-12-08 16:00 ` Kyle McMartin
2008-12-08 16:00 ` Kyle McMartin
2008-12-09 3:44 ` resource_size_t printk woes Kyle McMartin
2008-12-10 4:05 ` John David Anglin
2009-01-01 13:06 ` Helge Deller
2009-01-01 17:14 ` John David Anglin
2009-01-01 17:32 ` Helge Deller [this message]
2009-01-01 19:04 ` John David Anglin
2009-01-01 22:37 ` John David Anglin
2009-01-01 23:39 ` John David Anglin
2009-01-02 9:14 ` Helge Deller
2009-01-02 16:32 ` John David Anglin
2009-01-02 16:43 ` John David Anglin
2009-01-02 19:50 ` Grant Grundler
2008-12-08 4:50 ` 2.6.28-rcX in pretty bad shape on parisc John David Anglin
2008-12-08 7:50 ` Grant Grundler
2008-12-08 15:16 ` John David Anglin
2008-12-09 4:14 ` Kyle McMartin
2008-12-08 12:39 ` Carlos O'Donell
2008-12-08 14:54 ` John David Anglin
2008-12-08 15:02 ` Carlos O'Donell
2008-12-08 15:30 ` John David Anglin
2008-12-08 22:14 ` Carlos O'Donell
2008-12-08 22:39 ` John David Anglin
2008-12-09 0:01 ` Carlos O'Donell
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=495CFE20.2000702@gmx.de \
--to=deller@gmx.de \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=kyle@infradead.org \
--cc=linux-parisc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.