From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Paul Martin <paul.martin@codethink.co.uk>, linux-mips@linux-mips.org
Subject: Re: [PATCH 1/6] MIPS: OCTEON: Tell the kernel build system we can do Little Endian
Date: Fri, 13 Mar 2015 20:48:04 +0300 [thread overview]
Message-ID: <550322D4.6060303@cogentembedded.com> (raw)
In-Reply-To: <1426268098-1603-2-git-send-email-paul.martin@codethink.co.uk>
Hello.
On 03/13/2015 08:34 PM, Paul Martin wrote:
> Update the Kconfig file so that the configure system will
> allow us to build the kernel little endian.
You didn't sign off on your patches, so they can't be applied.
WBR, Sergei
next prev parent reply other threads:[~2015-03-13 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 17:34 [PATCH 0/6] MIPS: OCTEON: Patches to enable Little Endian Paul Martin
2015-03-13 17:34 ` [PATCH 1/6] MIPS: OCTEON: Tell the kernel build system we can do " Paul Martin
2015-03-13 17:48 ` Sergei Shtylyov [this message]
2015-03-13 18:37 ` Aaro Koskinen
2015-03-13 17:34 ` [PATCH 2/6] MIPS: OCTEON: Ensure CPUs come up little endian Paul Martin
2015-03-13 18:44 ` Aaro Koskinen
2015-03-13 17:34 ` [PATCH 3/6] MIPS: OCTEON: Turn hardware bitfields and structures inside out Paul Martin
2015-03-13 17:34 ` [PATCH 4/6] MIPS: OCTEON: Set appropriate endianness in L2C registers Paul Martin
2015-03-13 17:34 ` [PATCH 5/6] MIPS: OCTEON: Reverse the order of register accesses to the FAU Paul Martin
2015-03-13 17:34 ` [PATCH 6/6] MIPS: OCTEON: Set up ethernet hardware for little endian Paul Martin
2015-03-13 18:52 ` [PATCH 0/6] MIPS: OCTEON: Patches to enable Little Endian Aaro Koskinen
2015-03-16 10:39 ` Paul Martin
2015-03-16 19:27 ` Aaro Koskinen
2015-03-16 19:44 ` David Daney
2015-03-16 21:10 ` Aaro Koskinen
2015-03-16 22:02 ` David Daney
2015-03-16 14:57 ` Paul Martin
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=550322D4.6060303@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-mips@linux-mips.org \
--cc=paul.martin@codethink.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.