Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	Russell King <rmk@arm.linux.org.uk>,
	"tony.luck" <tony.luck@intel.com>
Subject: Re: [PATCHv4 6/6] byteorder: add copy_{endian} helpers
Date: Wed, 4 Jun 2008 21:34:58 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806042133510.32459@anakin> (raw)
In-Reply-To: <1212604681.6340.28.camel@brick>

On Wed, 4 Jun 2008, Harvey Harrison wrote:
> On Mon, 2008-06-02 at 21:15 +0200, Geert Uytterhoeven wrote:
> > On Mon, 2 Jun 2008, Harvey Harrison wrote:
> > > Add helpers for the idiom:
> > > *(__le16 *)ptr = cpu_to_le16(val);
> > > 
> > > Can now be written as:
> > > copy_le16(ptr, val);
> > 
> > Copy a little endian 16-bit value?
> > 
> > It doesn't just copy. It does a byteswap during the copy.
> 
> True, I had originally called this put_le16.  akpm suggested copy_le16.
> What do people think of copy_as_le16?

Sounds still a bit strange to me...

As `get' and `put' have connotations of reference counts, what about
`load' and `store', e.g. `load_le32()' and `store_be16()'?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2008-06-04 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 17:37 [PATCHv4 6/6] byteorder: add copy_{endian} helpers Harvey Harrison
2008-06-02 19:15 ` Geert Uytterhoeven
2008-06-04 18:38   ` Harvey Harrison
2008-06-04 19:34     ` Geert Uytterhoeven [this message]
2008-06-04 19:39       ` Harvey Harrison
2008-06-04 23:20         ` Russell King
2008-06-04 23:27           ` Harvey Harrison

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=Pine.LNX.4.64.0806042133510.32459@anakin \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=tony.luck@intel.com \
    /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