From: Andy Grover <andy.grover@oracle.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
rds-devel@oss.oracle.com, "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH 4/5] rds: stop including asm-generic/bitops/le.h directly
Date: Fri, 08 Oct 2010 11:55:55 -0700 [thread overview]
Message-ID: <4CAF693B.9030706@oracle.com> (raw)
In-Reply-To: <1286532193-29814-4-git-send-email-akinobu.mita@gmail.com>
On 10/08/2010 03:03 AM, Akinobu Mita wrote:
> asm-generic/bitops/le.h is only intended to be included directly from
> asm-generic/bitops/ext2-non-atomic.h or asm-generic/bitops/minix-le.h
> which implements generic ext2 or minix bit operations.
>
> This stops including asm-generic/bitops/le.h directly and use ext2
> non-atomic bit operations instead.
>
> An alternative approach is introducing little endian bit operations
> in linux/bitops.h. But it needs to touch more files than this change does.
> - generic___set_le_bit(off, (void *)map->m_page_addrs[i]);
> + ext2_set_bit(off, (void *)map->m_page_addrs[i]);
I'd like a solution that doesn't have rds calling a function starting
with ext2_. Seems wrong.
Thanks -- Regards -- Andy
next prev parent reply other threads:[~2010-10-08 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1286532193-29814-1-git-send-email-akinobu.mita@gmail.com>
2010-10-08 10:03 ` [PATCH 4/5] rds: stop including asm-generic/bitops/le.h directly Akinobu Mita
2010-10-08 18:55 ` Andy Grover [this message]
2010-10-08 18:59 ` David Miller
2010-10-10 15:09 ` Akinobu Mita
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=4CAF693B.9030706@oracle.com \
--to=andy.grover@oracle.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).