From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 2/5] spi: cadence_qspi: Fix fdt read of spi-max-frequency
Date: Sat, 17 Oct 2015 07:46:29 -0500 [thread overview]
Message-ID: <1445085989.2096.2.camel@clsee-VirtualBox> (raw)
In-Reply-To: <201510170108.53683.marex@denx.de>
Hi Marek,
On Sat, 2015-10-17 at 01:08 +0200, marex at denx.de wrote:
> On Friday, October 16, 2015 at 12:13:24 PM, Chin Liang See wrote:
> > From 4a91b5a380e7d3178d4378df79224442c79278bb Mon Sep 17 00:00:00 2001
> > From: Chin Liang See <clsee@altera.com>
> > Date: Fri, 16 Oct 2015 16:35:10 +0800
> > Subject: [PATCH v4 2/5] spi: cadence_qspi: Fix fdt read of
> > spi-max-frequency
> >
> > Fix the fdt read for spi-max-frequency as it's contained
> > in the child node. Current state of code is always
> > returning default value.
> >
> > Signed-off-by: Chin Liang See <clsee@altera.com>
> > Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
> > Cc: Dinh Nguyen <dinh.linux@gmail.com>
> > Cc: Marek Vasut <marex@denx.de>
> > Cc: Stefan Roese <sr@denx.de>
> > Cc: Vikas Manocha <vikas.manocha@st.com>
> > Cc: Jagannadh Teki <jteki@openedev.com>
> > Cc: Pavel Machek <pavel@denx.de>
> > Acked-by: Marek Vasut <marex@denx.de>
> > Acked-by: Pavel Machek <pavel@denx.de>
> > ---
> > Changes for v4
> > - use the newly created fdtdec_get_uint
>
> This patch depends on 5/5, so this will break bisect . Please do
> reorder the patches , most likely such that 5/5 goes in first and
> the rest follows.
>
Sure, I can do the patches order re-shuffling.
Thanks
Chin Liang
> Best regards,
> Marek Vasut
next prev parent reply other threads:[~2015-10-17 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1444987199-2728-1-git-send-email-clsee@altera.com>
2015-10-16 10:13 ` [U-Boot] [PATCH v4 2/5] spi: cadence_qspi: Fix fdt read of spi-max-frequency Chin Liang See
2015-10-16 23:08 ` Marek Vasut
2015-10-17 12:46 ` Chin Liang See [this message]
2015-10-17 12:54 ` Marek Vasut
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=1445085989.2096.2.camel@clsee-VirtualBox \
--to=clsee@altera.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.