From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-cfi-flash/master
Date: Thu, 10 Jan 2013 15:37:30 +0100 [thread overview]
Message-ID: <50EED22A.9070203@denx.de> (raw)
Hi Tom,
please pull the following patches pending for quite some time:
The following changes since commit 642ef40bdc95bef829ae3aadc217f829c4c298c4:
Merge branch 'master' of git://git.denx.de/u-boot-arm (2013-01-09 08:13:22 -0700)
are available in the git repository at:
git://www.denx.de/git/u-boot-cfi-flash.git master
for you to fetch changes up to d2af028db3f75390f56f018e16c0f269521e07c5:
cfi_flash: Report Advanced Sector Protection (PPB) with flinfo cmd (2013-01-10 14:40:00 +0100)
----------------------------------------------------------------
Angelo Dureghello (1):
mtd/cfi: add support for SST 4KB sector granularity
Stefan Roese (4):
cfi_flash: Add manufact_match helper function
cfi_flash: Read PPB sector protection from device for AMD/Spansion chips
cfi_flash: Enable PPB protection for all AMD cmdset flash chips
cfi_flash: Report Advanced Sector Protection (PPB) with flinfo cmd
drivers/mtd/cfi_flash.c | 71 ++++++++++++++++++++++++++++++++++++++++---------
include/flash.h | 1 +
2 files changed, 59 insertions(+), 13 deletions(-)
next reply other threads:[~2013-01-10 14:37 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 14:37 Stefan Roese [this message]
2013-01-10 21:44 ` [U-Boot] Please pull u-boot-cfi-flash/master Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2018-04-16 11:25 Stefan Roese
2018-04-16 16:43 ` Tom Rini
2018-01-29 12:35 Stefan Roese
2018-01-29 16:55 ` Tom Rini
2017-12-04 6:44 Stefan Roese
2017-12-04 18:36 ` Tom Rini
2017-09-26 15:59 Stefan Roese
2017-09-27 2:45 ` Tom Rini
2017-08-22 10:11 Stefan Roese
2017-08-26 20:44 ` Tom Rini
2017-08-08 12:32 Stefan Roese
2017-08-09 15:26 ` Tom Rini
2016-07-20 9:24 Stefan Roese
2016-07-20 12:13 ` Tom Rini
2016-04-13 12:04 Stefan Roese
2016-04-13 19:47 ` Tom Rini
2015-11-30 12:02 Stefan Roese
2015-11-30 20:17 ` Tom Rini
2013-05-23 7:55 Stefan Roese
2013-05-24 0:29 ` Tom Rini
2013-04-22 9:10 Stefan Roese
2013-04-22 17:51 ` Tom Rini
2013-04-12 17:13 Stefan Roese
2013-04-12 18:27 ` Tom Rini
2013-04-04 5:10 Stefan Roese
2013-04-05 16:28 ` Tom Rini
2013-04-12 9:35 ` Wolfgang Denk
2013-04-12 9:43 ` Stefan Roese
2013-04-12 14:37 ` Tom Rini
2013-04-12 17:00 ` Stefan Roese
2013-04-02 14:41 Stefan Roese
2013-04-02 18:17 ` Tom Rini
2012-09-03 9:43 Stefan Roese
2012-09-03 19:23 ` Wolfgang Denk
2012-08-13 12:56 Stefan Roese
2012-08-13 19:39 ` Wolfgang Denk
2012-03-21 15:28 Stefan Roese
2012-03-23 20:59 ` Wolfgang Denk
2011-03-28 17:34 Stefan Roese
2011-03-31 7:01 ` Wolfgang Denk
2010-10-12 7:01 Stefan Roese
2010-10-12 18:50 ` Wolfgang Denk
2010-08-12 12:05 Stefan Roese
2010-08-12 21:04 ` Wolfgang Denk
2010-08-13 7:36 ` Stefan Roese
2010-08-13 10:10 ` Wolfgang Denk
2010-04-07 9:35 Stefan Roese
2010-04-07 22:26 ` Wolfgang Denk
2010-03-25 8:47 Stefan Roese
2010-03-27 23:11 ` Wolfgang Denk
2010-03-04 9:12 Stefan Roese
2010-02-02 8:15 Stefan Roese
2010-02-03 19:21 ` Wolfgang Denk
2009-11-17 15:17 Stefan Roese
2009-11-17 21:36 ` Wolfgang Denk
2009-10-28 10:40 Stefan Roese
2009-10-28 20:53 ` Wolfgang Denk
2009-08-13 7:38 Stefan Roese
2009-08-13 18:52 ` Wolfgang Denk
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=50EED22A.9070203@denx.de \
--to=sr@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