From: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 01/14] MIPS: initialize board_init_f() argument to zero.
Date: Thu, 21 Jan 2016 15:06:55 +0100 [thread overview]
Message-ID: <1453385215.4370.3.camel@gmail.com> (raw)
In-Reply-To: <56973223.1090907@microchip.com>
Hi Purna,
Am Donnerstag, den 14.01.2016, 10:59 +0530 schrieb Purna Chandra
Mandal:
> On 01/12/2016 05:59 PM, Daniel Schwierzeck wrote:
>
> > 2016-01-12 11:18 GMT+01:00 Purna Chandra Mandal <
> > purna.mandal at microchip.com>:
> > > Signed-off-by: Purna Chandra Mandal <purna.mandal@microchip.com>
> > > ---
> > >
> > > Changes in v3: None
> > > Changes in v2: None
> > >
> > > arch/mips/cpu/start.S | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/arch/mips/cpu/start.S b/arch/mips/cpu/start.S
> > > index e95cdca..35d9650 100644
> > > --- a/arch/mips/cpu/start.S
> > > +++ b/arch/mips/cpu/start.S
> > > @@ -185,6 +185,8 @@ reset:
> > > PTR_ADDU t0, k0, GD_MALLOC_BASE # gd->malloc_base offset
> > > sw sp, 0(t0)
> > > #endif
> > > + /* Initialize args to zero */
> > > + move a0, zero
> > the comment should be on the same line and more precise. That is
> > useful in disassemblies or when debugging. E.g.
> >
> > move a0, zero # a0 <-- boot_flags = 0
> >
> > Also add a commit message please explaining why the change is
> > required. Something like that the boot_flags of board_init_f should
> > be
> > set to 0 because $a0 may be utilized in lowlevel_init or
> > mips_cache_reset.
>
> ack. Will add accordingly,
>
can you send an updated version as separate patch promptly? I'd like to
apply this patch as soon as possible because I have some follow-up
patches for start.S. Thanks.
--
- Daniel
next prev parent reply other threads:[~2016-01-21 14:06 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 10:18 [U-Boot] [PATCH v3 00/14] Initial Microchip PIC32MZ[DA] Support Purna Chandra Mandal
2016-01-12 10:18 ` [U-Boot] [PATCH v3 01/14] MIPS: initialize board_init_f() argument to zero Purna Chandra Mandal
2016-01-12 12:29 ` Daniel Schwierzeck
2016-01-14 5:29 ` Purna Chandra Mandal
2016-01-21 14:06 ` Daniel Schwierzeck [this message]
2016-01-12 10:18 ` [U-Boot] [PATCH v3 02/14] MIPS: initial infrastructure for Microchip PIC32 architecture Purna Chandra Mandal
2016-01-12 12:55 ` Daniel Schwierzeck
2016-01-13 14:56 ` Tom Rini
2016-01-12 10:18 ` [U-Boot] [PATCH v3 03/14] drivers: clk: Add clock driver for Microchip PIC32 Microcontroller Purna Chandra Mandal
2016-01-13 13:38 ` Daniel Schwierzeck
2016-01-14 5:34 ` Purna Chandra Mandal
2016-01-13 14:55 ` Tom Rini
2016-01-14 6:04 ` Purna Chandra Mandal
2016-01-14 12:30 ` Tom Rini
2016-01-12 10:18 ` [U-Boot] [PATCH v3 04/14] drivers: pinctrl: Add pinctrl driver for Microchip PIC32 Purna Chandra Mandal
2016-01-13 13:42 ` Daniel Schwierzeck
2016-01-13 14:55 ` Tom Rini
2016-01-13 20:10 ` Simon Glass
2016-01-12 10:18 ` [U-Boot] [PATCH v3 05/14] drivers: gpio: add driver for Microchip PIC32 GPIO controller Purna Chandra Mandal
2016-01-13 13:46 ` Daniel Schwierzeck
2016-01-13 14:08 ` Daniel Schwierzeck
2016-01-14 5:41 ` Purna Chandra Mandal
2016-01-13 14:55 ` Tom Rini
2016-01-13 20:10 ` Simon Glass
2016-01-14 10:15 ` Purna Chandra Mandal
2016-01-12 10:18 ` [U-Boot] [PATCH v3 06/14] drivers: serial: add driver for Microchip PIC32 UART controller Purna Chandra Mandal
2016-01-13 13:49 ` Daniel Schwierzeck
2016-01-13 14:03 ` Daniel Schwierzeck
2016-01-14 5:42 ` Purna Chandra Mandal
2016-01-13 14:55 ` Tom Rini
2016-01-13 20:09 ` Simon Glass
2016-01-14 6:14 ` Purna Chandra Mandal
2016-01-12 10:18 ` [U-Boot] [PATCH v3 07/14] drivers: ddr: Add DDR2 SDRAM controller driver for Microchip PIC32 Purna Chandra Mandal
2016-01-13 13:53 ` Daniel Schwierzeck
2016-01-13 14:55 ` Tom Rini
2016-01-13 20:09 ` Simon Glass
2016-01-12 10:18 ` [U-Boot] [PATCH v3 08/14] MIPS: Add support for Microchip PIC32MZ[DA] SoC family Purna Chandra Mandal
2016-01-13 14:49 ` Daniel Schwierzeck
2016-01-14 5:54 ` Purna Chandra Mandal
2016-01-12 10:18 ` [U-Boot] [PATCH v3 09/14] board: Add Microchip PIC32MZ[DA]-Starter-Kit board Purna Chandra Mandal
2016-01-13 14:56 ` Tom Rini
2016-01-14 6:40 ` Purna Chandra Mandal
2016-01-13 15:03 ` Daniel Schwierzeck
2016-01-14 8:40 ` Purna Chandra Mandal
2016-01-12 10:18 ` [U-Boot] [PATCH v3 10/14] drivers: mmc: add driver for Microchip PIC32 SDHCI controller Purna Chandra Mandal
2016-01-13 14:56 ` Tom Rini
2016-01-13 15:15 ` Daniel Schwierzeck
2016-01-14 9:18 ` Purna Chandra Mandal
2016-01-12 10:18 ` [U-Boot] [PATCH v3 11/14] board: add SDHCI support for PIC32MZDASK board Purna Chandra Mandal
2016-01-13 14:56 ` Tom Rini
2016-01-14 8:31 ` Purna Chandra Mandal
2016-01-12 10:18 ` [U-Boot] [PATCH v3 12/14] drivers: net: phy: add SMSC LAN8740 Phy support Purna Chandra Mandal
2016-01-13 14:56 ` Tom Rini
2016-01-13 15:19 ` Daniel Schwierzeck
2016-01-12 10:18 ` [U-Boot] [PATCH v3 13/14] drivers: net: Add ethernet driver for Microchip PIC32 Purna Chandra Mandal
2016-01-13 14:56 ` Tom Rini
2016-01-14 10:29 ` Purna Chandra Mandal
2016-01-13 15:37 ` Daniel Schwierzeck
2016-01-14 10:05 ` Purna Chandra Mandal
2016-01-14 14:01 ` Daniel Schwierzeck
2016-01-12 10:18 ` [U-Boot] [PATCH v3 14/14] board: Enable ethernet, tftpboot support to pic32mzdask board Purna Chandra Mandal
2016-01-13 14:56 ` Tom Rini
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=1453385215.4370.3.camel@gmail.com \
--to=daniel.schwierzeck@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox