From: Harvey Harrison <harvey.harrison@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc drivers/net endianness noise
Date: Tue, 20 May 2008 17:58:21 -0700 [thread overview]
Message-ID: <1211331501.5915.248.camel@brick> (raw)
In-Reply-To: <20080521005502.GF28946@ZenIV.linux.org.uk>
On Wed, 2008-05-21 at 01:55 +0100, Al Viro wrote:
> On Tue, May 20, 2008 at 05:48:00PM -0700, Harvey Harrison wrote:
> > I was contemplating an api like:
> >
> > void put_le16(u16 val, __le16 *ptr)
> > {
> > *ptr = cpu_to_le16(val);
> > }
> >
> > which would allow the above to become:
> >
> > if (catc->is_f5u011)
> > put_be16(skb->len, tx_buf);
> > else
> > put_le16(skb->len, tx_buf);
> >
> > Thoughts?
>
> Do not grow API too much. Mental savings on recognizing what's done are
> offset by need to remember more helper functions...
Fair point, I was hoping to get the following family:
get_le16
put_le16
get_unaligned_le16
put_unaligned_le16
And get rid of the le16_to_cpup api.
Then the it's explicit when alignment is an issue, and the endianess is
also explicit. That and I think it just looks nicer than the existing
*p versions.
Just a thought,
Harvey
next prev parent reply other threads:[~2008-05-21 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 0:34 [PATCH] misc drivers/net endianness noise Al Viro
2008-05-21 0:48 ` Harvey Harrison
2008-05-21 0:55 ` Al Viro
2008-05-21 0:58 ` Harvey Harrison [this message]
2008-05-22 11:09 ` Jeff Garzik
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=1211331501.5915.248.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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