linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@firmix.at>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Andrew Morton <akpm@osdl.org>,
	ext2-devel@lists.sourceforge.net, Jeff Mahoney <jeffm@suse.com>,
	linux-kernel@vger.kernel.org, cmm@us.ibm.com,
	linux-fsdevel@vger.kernel.org,
	Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH 2/9] sector_t format string
Date: Fri, 11 Aug 2006 10:31:47 +0200	[thread overview]
Message-ID: <1155285107.12126.0.camel@tara.firmix.at> (raw)
In-Reply-To: <Pine.LNX.4.61.0608110757090.21588@yvahk01.tjqt.qr>

On Fri, 2006-08-11 at 07:57 +0200, Jan Engelhardt wrote:
> >> Will
> >> 
> >> 	printk("%S", sector_t);
> >> 
> >> kill at least one kitten?
> >
> >I like the general idea. I think that having to cast every time you want
> >to print a sector number is pretty gross. I had something more like %Su
> >in mind, though.
> 
> What will happen if you run out of %[a-z] ?

My keyboard can produce a lot more characters (even if I ignore the
non-ASCII ones).

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-08-11  8:31 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  1:20 [PATCH 2/9] sector_t format string Mingming Cao
2006-08-10  6:40 ` Andrew Morton
2006-08-10 11:05   ` Roman Zippel
2006-08-10 12:02     ` Jeff Garzik
2006-08-10 12:24       ` Roman Zippel
2006-08-10 12:25         ` Jeff Garzik
2006-08-10 12:30           ` Roman Zippel
2006-08-10 12:33             ` Jeff Garzik
2006-08-10 13:08               ` Roman Zippel
2006-08-10 13:14                 ` Jeff Garzik
2006-08-10 13:27                   ` Roman Zippel
2006-08-10 13:30                     ` Jeff Garzik
2006-08-10 13:52                       ` Roman Zippel
2006-08-10 14:04                         ` [Ext2-devel] " Eric Sandeen
2006-08-10 14:19                           ` Roman Zippel
2006-08-10 14:21                             ` Jeff Garzik
2006-08-10 14:35                               ` Roman Zippel
2006-08-10 14:06                         ` Jeff Garzik
2006-08-10 14:24                           ` Roman Zippel
2006-08-10 14:26                             ` Jeff Garzik
2006-08-10 14:41                               ` Roman Zippel
2006-08-10 16:24                     ` John Stoffel
2006-08-10 16:43                       ` Roman Zippel
2006-08-10 16:54                       ` Andrew Morton
2006-08-10 17:24                         ` Roman Zippel
2006-08-10 15:31   ` [Ext2-devel] " Theodore Tso
2006-08-10 16:37     ` Roman Zippel
2006-08-10 21:59       ` [Ext2-devel] " Mingming Cao
2006-08-10 19:17   ` Joel Becker
2006-08-10 19:44     ` Alexey Dobriyan
2006-08-10 19:57       ` Andrew Morton
2006-08-10 20:41         ` Alexey Dobriyan
2006-08-10 20:17       ` Jeff Mahoney
2006-08-11  5:57         ` Jan Engelhardt
2006-08-11  8:31           ` Bernd Petrovitsch [this message]
2006-08-11  9:07             ` Jan Engelhardt
2006-08-11 14:48           ` Jeff Mahoney
2006-08-11  0:59   ` Mingming Cao
2006-08-11  2:11     ` Eric Sandeen
2006-08-11 22:06     ` Mingming Cao

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=1155285107.12126.0.camel@tara.firmix.at \
    --to=bernd@firmix.at \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=cmm@us.ibm.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=jeffm@suse.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).