public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: David Miller <davem@davemloft.net>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] byteorder: eliminate pointer bytorder api
Date: Tue, 27 May 2008 15:40:16 -0700	[thread overview]
Message-ID: <1211928016.5964.6.camel@brick> (raw)
In-Reply-To: <alpine.LNX.1.10.0805261416370.19084@fbirervta.pbzchgretzou.qr>

On Mon, 2008-05-26 at 14:17 +0200, Jan Engelhardt wrote:
> On Wednesday 2008-05-21 00:30, Harvey Harrison wrote:
> >On Tue, 2008-05-20 at 15:19 -0700, David Miller wrote:
> >> From: Harvey Harrison <harvey.harrison@gmail.com>
> >> Date: Tue, 20 May 2008 15:15:25 -0700
> >> 
> >> > Obviously I missed that part, my apologies.  Would it be acceptable if,
> >> > taking the possibly arch-specific parts, moved the [endian]_to_cpup
> >> > name over to get_[endian]
> >> 
> >> Why are we fiddling with interface names that have been fine for about
> >> 10 years?
> 
> I suggest some comments be added to the cpu_to_*p() to specify their 
> reason for being there (namely, speedups on some CPUs)

Agreed.

> 
> >Saw a lot of (or similar in a private helper):
> >
> >*(__be32 *)ptr = cpu_to_be32(val);
> >
> >So I came up with
> >
> >void put_be32(val, ptr);
> 
> I think it would be better to follow the common notation of the target 
> being on the left side (like most intel asm commands and things like 
> C's memcpy, etc)

I based this on the existing put_unaligned_be32 to have the same arg
order.

Cheers,

Harvey


      reply	other threads:[~2008-05-27 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 19:24 [PATCH 2/2] byteorder: eliminate pointer bytorder api Harvey Harrison
2008-05-20 21:17 ` David Miller
2008-05-20 22:15   ` Harvey Harrison
2008-05-20 22:19     ` David Miller
2008-05-20 22:30       ` Harvey Harrison
2008-05-26 12:17         ` Jan Engelhardt
2008-05-27 22:40           ` 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=1211928016.5964.6.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=jengelh@medozas.de \
    --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