From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Joe Perches <joe@perches.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: byteorder: cpu_to_le32_array vs cpu_to_be32_array function API differences
Date: Mon, 21 Oct 2019 12:31:30 +0300 [thread overview]
Message-ID: <20191021093130.GL32742@smile.fi.intel.com> (raw)
In-Reply-To: <2acb30fb3c9a86ac8cc882fb787cd04e5864224b.camel@perches.com>
On Sun, Oct 20, 2019 at 12:02:52PM -0700, Joe Perches wrote:
> There's an argument inconsistency between these 4 functions
> in include/linux/byteorder/generic.h
>
> It'd be more a consistent API with one form and not two.
This is done in order to:
- avoid changing existing code
- start a very this discussion to see what we can do if it's even needed to be done
So, do we have other places in the kernel which can utilize either of these?
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2019-10-21 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 19:02 Joe Perches
2019-10-20 19:28 ` Anatol Belski
2019-10-20 19:40 ` Joe Perches
2019-10-20 20:23 ` Anatol Belski
2019-10-21 9:31 ` Andy Shevchenko [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=20191021093130.GL32742@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.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
all inboxes | Powered by JetHome®