From: Jagan Teki <jagan@openedev.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: u-boot-spi/next
Date: Mon, 8 May 2017 21:46:41 +0530 [thread overview]
Message-ID: <1494260201-3154-1-git-send-email-jagan@openedev.com> (raw)
Hi Tom,
Please take this PR.
thanks!
Jagan.
The following changes since commit ac6991fb5fc1a694b29f4ebd5e07baebf818d7cc:
zynq: spi: Honour the activation / deactivation delay (2017-05-03 11:03:04 +0530)
are available in the git repository at:
git://git.denx.de/u-boot-spi.git next
for you to fetch changes up to 0b2e5bbe6a4f3d25522675198b8beb0093a2e750:
env_sf: use DIV_ROUND_UP to calculate number of sectors to erase (2017-05-03 11:18:20 +0530)
----------------------------------------------------------------
Andreas Fenkart (4):
env_sf: factor out prepare_flash_device
enf_sf: reuse setup_flash_device instead of open coding it
env_sf: re-order error handling in single-buffer env_relocate_spec
env_sf: use DIV_ROUND_UP to calculate number of sectors to erase
common/env_sf.c | 92 ++++++++++++++++++++++-----------------------------------
1 file changed, 36 insertions(+), 56 deletions(-)
next reply other threads:[~2017-05-08 16:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 16:16 Jagan Teki [this message]
2017-05-09 0:12 ` [U-Boot] Pull request: u-boot-spi/next Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2015-12-30 10:31 Jagan Teki
2015-12-30 10:34 ` Jagan Teki
2015-12-31 17:54 ` Jagan Teki
2016-01-02 17:04 ` Tom Rini
2016-01-03 3:56 ` Jagan Teki
2016-01-03 14:44 ` Tom Rini
2016-01-03 15:40 ` Jagan Teki
2016-01-03 15:56 ` Tom Rini
2016-01-06 9:24 ` Jagan Teki
2015-11-03 18:09 Jagan Teki
2015-11-04 1:47 ` Tom Rini
2015-11-04 2:01 ` Bin Meng
2015-11-04 3:45 ` Fabio Estevam
2015-11-04 10:46 ` Fabio Estevam
2015-11-04 10:47 ` Fabio Estevam
2015-11-04 11:08 ` Fabio Estevam
2015-11-04 11:17 ` Jagan Teki
2015-11-04 11:21 ` Fabio Estevam
2015-11-04 11:30 ` Jagan Teki
2015-11-04 11:35 ` Fabio Estevam
2015-11-04 14:01 ` Fabio Estevam
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=1494260201-3154-1-git-send-email-jagan@openedev.com \
--to=jagan@openedev.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