From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-cfi-flash/master
Date: Mon, 4 Dec 2017 13:36:54 -0500 [thread overview]
Message-ID: <20171204183654.GE3587@bill-the-cat> (raw)
In-Reply-To: <51fbd310-cb3e-3a63-9679-c467d0a692db@denx.de>
On Mon, Dec 04, 2017 at 07:44:50AM +0100, Stefan Roese wrote:
> Hi Tom,
>
> please pull this one CFI driver fix from York.
>
> Thanks,
> Stefan
>
> The following changes since commit b06c46de632c55f4c39d404c6f0f65e414b31050:
>
> Merge tag 'xilinx-for-v2018.01' of git://www.denx.de/git/u-boot-microblaze (2017-11-29 08:26:07 -0500)
>
> are available in the Git repository at:
>
> git://www.denx.de/git/u-boot-cfi-flash.git
>
> for you to fetch changes up to 2544f47078635958bacb106684a2f81f57a4ed80:
>
> mtd: cfi: Fix checking status register feature (2017-12-04 07:41:32 +0100)
>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171204/315d7f91/attachment.sig>
next prev parent reply other threads:[~2017-12-04 18:36 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 6:44 [U-Boot] Please pull u-boot-cfi-flash/master Stefan Roese
2017-12-04 18:36 ` Tom Rini [this message]
-- 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-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
2013-01-10 14:37 Stefan Roese
2013-01-10 21:44 ` 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=20171204183654.GE3587@bill-the-cat \
--to=trini@konsulko.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