From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: socfpga: Enabling U-Boot environment support in QSPI
Date: Fri, 26 Feb 2016 19:08:27 +0100 [thread overview]
Message-ID: <56D0949B.1070901@denx.de> (raw)
In-Reply-To: <1456491989.2338.2.camel@altera.com>
On 02/26/2016 02:06 PM, Chin Liang See wrote:
> On Wed, 2016-02-24 at 18:44 +0100, Marek Vasut wrote:
>> On 02/24/2016 09:50 AM, Chin Liang See wrote:
>>> Enabling the support of storing U-Boot environment
>>> within serial NOR flash. By default, its still
>>> store into SDMMC
>>>
>>> Signed-off-by: Chin Liang See <clsee@altera.com>
>>> Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
>>> Cc: Dinh Nguyen <dinh.linux@gmail.com>
>>> Cc: Pavel Machek <pavel@denx.de>
>>> Cc: Marek Vasut <marex@denx.de>
>>> Cc: Stefan Roese <sr@denx.de>
>>
>> I am fine with the patch, but why did I receive it thrice ? ;-)
>>
>
> Sorry about this as I thought IT blocked the email sending. I noticed
> the U-Boot mailing didn't show the patch after 10 mins. I was surprised
> to see 3 and guess it took longer time to go through IT servers
> screening :)
Gotcha!
btw I started screening the patches a bit more. socfpga_sr1500 produces
a warning with this patch.
Please use buildman to build your patches, something like:
./tools/buildman/buildman -b u-boot/master..HEAD -defsS "socfpga"
will do the trick.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-02-26 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 8:50 [U-Boot] [PATCH] arm: socfpga: Enabling U-Boot environment support in QSPI Chin Liang See
2016-02-24 17:44 ` Marek Vasut
2016-02-26 13:06 ` Chin Liang See
2016-02-26 18:08 ` Marek Vasut [this message]
2016-03-01 6:38 ` Chin Liang See
2016-03-01 13:51 ` Marek Vasut
2016-03-02 12:25 ` Chin Liang See
-- strict thread matches above, loose matches on Subject: below --
2016-02-24 8:40 Chin Liang See
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=56D0949B.1070901@denx.de \
--to=marex@denx.de \
--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