From: Babu Moger <babu.moger@oracle.com>
To: monstr@monstr.eu, jejb@parisc-linux.org, deller@gmx.de,
davem@davemloft.net, akpm@linux-foundation.org
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH 2/2] arch: change default endian for microblaze
Date: Mon, 18 Sep 2017 13:05:45 -0500 [thread overview]
Message-ID: <e755625e-0b3a-4027-0754-4873fc8446b1@oracle.com> (raw)
In-Reply-To: <cf4bd066-b349-070a-ddf9-d6ae02f44cd7@monstr.eu>
On 9/18/2017 12:49 PM, Michal Simek wrote:
> On 18.9.2017 18:53, Babu Moger wrote:
>> Fix the default for microblaze. Michal Simek mentioned default for
>> microblaze should be CPU_LITTLE_ENDIAN.
>>
>> Fixes : commit 206d3642d8ee ("arch/microblaze: add choice for endianness
>> and update Makefile")
>>
>> Signed-off-by: Babu Moger <babu.moger@oracle.com>
>> Cc: Michal Simek <monstr@monstr.eu>
>> ---
>> arch/microblaze/Kconfig | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/microblaze/Kconfig b/arch/microblaze/Kconfig
>> index 9d26abd..4f798aa 100644
>> --- a/arch/microblaze/Kconfig
>> +++ b/arch/microblaze/Kconfig
>> @@ -39,7 +39,7 @@ config MICROBLAZE
>> # Endianness selection
>> choice
>> prompt "Endianness selection"
>> - default CPU_BIG_ENDIAN
>> + default CPU_LITTLE_ENDIAN
>> help
>> microblaze architectures can be configured for either little or
>> big endian formats. Be sure to select the appropriate mode.
>>
> Acked-by: Michal Simek <michal.simek@xilinx.com>
Thanks.
> If you want me to take this through my microblaze tree please let me know.
Sure. Thanks
>
> Thanks,
> Michal
>
next prev parent reply other threads:[~2017-09-18 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 16:53 [PATCH 0/2] Fix duplicates and " Babu Moger
2017-09-18 16:53 ` [PATCH 1/2] arch: Fix duplicates in Kconfig for parisc and sparc Babu Moger
2017-09-18 16:53 ` [PATCH 2/2] arch: change default endian for microblaze Babu Moger
2017-09-18 17:49 ` Michal Simek
2017-09-18 18:05 ` Babu Moger [this message]
2017-09-25 13:37 ` Michal Simek
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=e755625e-0b3a-4027-0754-4873fc8446b1@oracle.com \
--to=babu.moger@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=sparclinux@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
all inboxes | Powered by JetHome®