From: Greg KH <gregkh@linuxfoundation.org>
To: Babu Moger <babu.moger@oracle.com>
Cc: ysato@users.sourceforge.jp, geert@linux-m68k.org,
jonas@southpole.se, stefan.kristiansson@saunalahti.fi,
shorne@gmail.com, jejb@parisc-linux.org, deller@gmx.de,
davem@davemloft.net, viro@zeniv.linux.org.uk, monstr@monstr.eu,
mpe@ellerman.id.au, peterz@infradead.org, mingo@redhat.com,
jcmvbkbc@gmail.com, linux-kernel@vger.kernel.org,
uclinux-h8-devel@lists.sourceforge.jp,
linux-m68k@vger.kernel.org, openrisc@lists.librecores.org,
linux-parisc@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Define CPU_BIG_ENDIAN or warn for inconsistencies
Date: Tue, 29 Aug 2017 08:30:15 +0200 [thread overview]
Message-ID: <20170829063015.GA12198@kroah.com> (raw)
In-Reply-To: <1499358861-179979-1-git-send-email-babu.moger@oracle.com>
On Thu, Jul 06, 2017 at 09:34:18AM -0700, Babu Moger wrote:
> Resending the series per Greg KH's request.
>
> Found this problem while enabling queued rwlock on SPARC.
> The parameter CONFIG_CPU_BIG_ENDIAN is used to clear the
> specific byte in qrwlock structure. Without this parameter,
> we clear the wrong byte.
> Here is the code in include/asm-generic/qrwlock.h
>
> static inline u8 *__qrwlock_write_byte(struct qrwlock *lock)
> {
> return (u8 *)lock + 3 * IS_BUILTIN(CONFIG_CPU_BIG_ENDIAN);
> }
>
> Also found few more references of this parameter in
> drivers/of/base.c
> drivers/of/fdt.c
> drivers/tty/serial/earlycon.c
> drivers/tty/serial/serial_core.c
>
> Here is our previous discussion.
> https://lkml.org/lkml/2017/5/24/620
>
> Based on the discussion, it was decided to add CONFIG_CPU_BIG_ENDIAN
> for all the fixed big endian architecture(frv, h8300, m68k, openrisc,
> parisc and sparc). And warn if there are inconsistencies in this definition.
Did this series ever get picked up by anyone? I don't know whose tree
it should go through if not, anyone have any ideas? I guess I could,
but arch-specific stuff is odd...
thanks,
greg k-h
next prev parent reply other threads:[~2017-08-29 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 16:34 [PATCH v3 0/3] Define CPU_BIG_ENDIAN or warn for inconsistencies Babu Moger
2017-07-06 16:34 ` [PATCH v3 1/3] arch: Define CPU_BIG_ENDIAN for all fixed big endian archs Babu Moger
2017-07-06 16:34 ` [PATCH v3 2/3] arch/microblaze: Add choice for endianness and update Makefile Babu Moger
2017-07-06 16:34 ` [PATCH v3 3/3] include: warn for inconsistent endian config definition Babu Moger
2017-08-29 6:30 ` Greg KH [this message]
2017-08-29 9:04 ` [PATCH v3 0/3] Define CPU_BIG_ENDIAN or warn for inconsistencies Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2017-06-12 22:09 Babu Moger
2017-07-04 7:11 ` Geert Uytterhoeven
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=20170829063015.GA12198@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=babu.moger@oracle.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=jcmvbkbc@gmail.com \
--cc=jejb@parisc-linux.org \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=openrisc@lists.librecores.org \
--cc=peterz@infradead.org \
--cc=shorne@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=viro@zeniv.linux.org.uk \
--cc=ysato@users.sourceforge.jp \
/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