From: Purna Chandra Mandal <purna.mandal@microchip.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 02/18] MIPS: initial infrastructure for Microchip PIC32 architecture.
Date: Tue, 22 Dec 2015 19:21:16 +0530 [thread overview]
Message-ID: <56795554.6010102@microchip.com> (raw)
In-Reply-To: <56783058.5010801@gmail.com>
On 12/21/2015 10:31 PM, Daniel Schwierzeck wrote:
>
> Am 17.12.2015 um 18:28 schrieb Purna Chandra Mandal:
>> Signed-off-by: Purna Chandra Mandal <purna.mandal@microchip.com>
>> ---
>>
>> arch/mips/Kconfig | 5 ++
>> arch/mips/Makefile | 1 +
>> arch/mips/include/asm/arch-pic32/clock.h | 31 +++++++
>> arch/mips/include/asm/arch-pic32/pic32.h | 145 +++++++++++++++++++++++++++++++
>> arch/mips/mach-pic32/Kconfig | 20 +++++
>> arch/mips/mach-pic32/Makefile | 7 ++
>> arch/mips/mach-pic32/config.mk | 8 ++
>> arch/mips/mach-pic32/cpu.c | 13 +++
>> 8 files changed, 230 insertions(+)
>> create mode 100644 arch/mips/include/asm/arch-pic32/clock.h
>> create mode 100644 arch/mips/include/asm/arch-pic32/pic32.h
> I noticed in an other thread that CONFIG_ARCH_SYMLINKS is going to be
> deprecated. The preferred location for SoC specific header files is
> "arch/*/mach-*/include/mach/". A driver can then use "include
> <mach/file.h>".
>
> I've already sent a patch for MIPS [1]. So please rebase to
> u-boot-mips/next and move those two files to
> arch/mips/mach-pic32/include/mach/.
Thanks. Will rebase and update accordingly.
>> create mode 100644 arch/mips/mach-pic32/Kconfig
>> create mode 100644 arch/mips/mach-pic32/Makefile
>> create mode 100644 arch/mips/mach-pic32/config.mk
>> create mode 100644 arch/mips/mach-pic32/cpu.c
>>
> [1] http://patchwork.ozlabs.org/patch/559581/
>
prev parent reply other threads:[~2015-12-22 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 17:28 [U-Boot] [PATCH v1 02/18] MIPS: initial infrastructure for Microchip PIC32 architecture Purna Chandra Mandal
2015-12-19 23:19 ` Daniel Schwierzeck
2015-12-21 12:49 ` Purna Chandra Mandal
2015-12-22 13:38 ` Purna Chandra Mandal
2015-12-21 17:01 ` Daniel Schwierzeck
2015-12-22 13:51 ` Purna Chandra Mandal [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=56795554.6010102@microchip.com \
--to=purna.mandal@microchip.com \
--cc=u-boot@lists.denx.de \
/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.