From: Harvey Harrison <harvey.harrison@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 12/12] net: use the common ascii hex helpers
Date: Fri, 02 May 2008 17:15:55 -0700 [thread overview]
Message-ID: <1209773755.26173.114.camel@brick> (raw)
In-Reply-To: <20080502170802.456493a5.akpm@linux-foundation.org>
On Fri, 2008-05-02 at 17:08 -0700, Andrew Morton wrote:
> > > Yup. After a bit of testing and tyre-kicking I'll probably slip
> > > lib-add-ascii-hex-helper-functions.patch into mainline so that we can
> > > trickle all the *-use-the-common-ascii-hex-helpers.patch patches out to the
> > > various maintainers.
> > >
> >
> > I suppose the hex_asc array and hex_to_int could also use
> > EXPORT_SYMBOL().
>
> gack. How could you do all those patches without discovering this? Please
> go give your QA staff a wedgie.
Sorry about the fat-fingered send, as before:
allyesconfig :(
> yes, hex_to_u8() is more specific and better defined than hex_to_int().
>
> Although anally it should perhaps be two_digit_hex_to_ulong,
> four_digit_hex_to_ulong, etc.
>
> ho hum, I'll drop them all.
int hex_char_to_int(char ch)
{
return -1 if not [a-fA-F0-9]
}
int hex_to_u8(const char *buf, u8 *val)
int hex_to_u16(const char *buf, u16 *val)
int hex_to_u32(const char *buf, u32 *val)
int hex_to_u64(const char *buf, u64 *val)
Which return the number of chars read and reads up to a maximum of
2,4,8,16 chars respectively and returns early if a non-hex char
is encountered.
Thoughts?
Harvey
next prev parent reply other threads:[~2008-05-03 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 19:01 [PATCH 12/12] net: use the common ascii hex helpers Harvey Harrison
2008-05-02 23:25 ` David Miller
2008-05-02 23:31 ` Andrew Morton
2008-05-02 23:39 ` David Miller
2008-05-02 23:43 ` Andrew Morton
2008-05-02 23:52 ` Harvey Harrison
2008-05-03 0:08 ` Andrew Morton
2008-05-03 0:11 ` Harvey Harrison
2008-05-03 0:15 ` Harvey Harrison [this message]
2008-05-03 0:30 ` Andrew Morton
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=1209773755.26173.114.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--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