From: Harvey Harrison <harvey.harrison@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel: add helpers for ascii character conversion
Date: Thu, 01 May 2008 12:48:30 -0700 [thread overview]
Message-ID: <1209671310.24729.157.camel@brick> (raw)
In-Reply-To: <20080501124317.089a0d02.akpm@linux-foundation.org>
On Thu, 2008-05-01 at 12:43 -0700, Andrew Morton wrote:
> On Thu, 01 May 2008 12:23:00 -0700
> Harvey Harrison <harvey.harrison@gmail.com> wrote:
>
> > Add helpers for getting an ascii hex char for the high and low
> > nibble of a byte. Also add a small helper to get an integer
> > value from a given hex char.
> >
> > Included here are a few of the current places that roll their
> > own versions being moved to the common helper.
>
> ahh, someone cares ;)
Well, I have an interest in collecting bits of useful infrastructure
everyone and their dog has reimplemented somewhere in the tree.
>
> Does this mean that
>
> y:/usr/src/linux-2.6.25> grep -ri '"0123456789abcdef"' . | wc -l
> 40
>
> will decrease?
Somewhat, I debated between the kernel.h route and adding an out-of-line
version to hexdump.c. While gcc/ld has gotten better about this, may
as well make it easy.
>
> > --- a/include/linux/kernel.h
> > +++ b/include/linux/kernel.h
> > @@ -277,6 +277,21 @@ extern void print_hex_dump(const char *level, const char *prefix_str,
> > extern void print_hex_dump_bytes(const char *prefix_str, int prefix_type,
> > const void *buf, size_t len);
> > #define hex_asc(x) "0123456789abcdef"[x]
> > +#define hex_asc_lo(x) hex_asc(((x) & 0x0f))
> > +#define hex_asc_hi(x) hex_asc(((x) & 0xf0) >> 4)
>
> umm, this might mean that each .c file which uses hex_asc_lo/hi gets
> its own copy of "0123456789abcdef". I believe that gcc/ld are getting
> better at handling this, but I haven't checked, and I don't know which
> versions get it right nor in which way. etc.
>
> So it might be better to give the kernel the One True Digitstring in
> lib/something.c and export that to modules.
>
> > +static inline u8 hex_to_int(char ch)
> > +{
> > + /*
> > + * Make ch lower-case, works only for digits and letters
> > + */
> > + ch |= 0x20;
> > + if ((ch >= 'a') && (ch <= 'f'))
> > + return (ch - 'a' + 10);
> > + if ((ch >= '0') && (ch <= '9'))
> > + return (ch - '0');
> > + return (-1);
> > +}
>
> probably should be uninlined.
>
> return-is-not-a-function ;)
...you didn't even blink at my last-minute change from returning int
to u8 that was, how to say, ill-advised now that I look again :(
In any event, I'll go the lib/hexdump route and send that in a bit.
Cheers,
Harvey
prev parent reply other threads:[~2008-05-01 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 19:23 [PATCH] kernel: add helpers for ascii character conversion Harvey Harrison
2008-05-01 19:43 ` Andrew Morton
2008-05-01 19:48 ` Harvey Harrison [this message]
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=1209671310.24729.157.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.