From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: u-boot-staging
Date: Sat, 11 Aug 2018 19:15:26 +0200 [thread overview]
Message-ID: <20180811191526.40c74448@crub> (raw)
Hi Tom,
The following changes since commit a032e0a6aed208977f48e78d2cc497b91543beaf:
travis: give every job a name (2018-08-10 13:50:30 -0400)
are available in the git repository at:
git://git.denx.de/u-boot-staging.git agust at denx.de
for you to fetch changes up to 7e86242b2bdb2983423a3a1f3ec375df56c7cac8:
misc: Add gdsys_ioep driver (2018-08-11 16:00:50 +0200)
----------------------------------------------------------------
Mario Six (4):
misc: docs: Fix comments in misc.h
misc: uclass: Add enable/disable function
test: Add tests for misc uclass
misc: Add gdsys_ioep driver
.../devicetree/bindings/misc/gdsys,io-endpoint.txt | 20 ++
arch/sandbox/dts/test.dts | 4 +
drivers/misc/Kconfig | 6 +
drivers/misc/Makefile | 3 +-
drivers/misc/gdsys_ioep.c | 209 +++++++++++++++++++++
drivers/misc/gdsys_ioep.h | 137 ++++++++++++++
drivers/misc/misc-uclass.c | 10 +
drivers/misc/misc_sandbox.c | 133 +++++++++++++
include/misc.h | 109 +++++++----
test/dm/Makefile | 1 +
test/dm/misc.c | 83 ++++++++
11 files changed, 675 insertions(+), 40 deletions(-)
create mode 100644 Documentation/devicetree/bindings/misc/gdsys,io-endpoint.txt
create mode 100644 drivers/misc/gdsys_ioep.c
create mode 100644 drivers/misc/gdsys_ioep.h
create mode 100644 drivers/misc/misc_sandbox.c
create mode 100644 test/dm/misc.c
Please pull. Thanks!
--
Anatolij
next reply other threads:[~2018-08-11 17:15 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 17:15 Anatolij Gustschin [this message]
2018-08-13 0:21 ` [U-Boot] Pull request: u-boot-staging Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2019-06-10 11:26 Anatolij Gustschin
2019-06-10 13:42 ` Tom Rini
2019-06-10 13:50 ` Anatolij Gustschin
2018-10-20 19:35 Anatolij Gustschin
2018-10-20 19:43 ` Tom Rini
2018-10-20 20:20 ` Anatolij Gustschin
2018-10-22 18:26 ` Jagan Teki
2018-10-22 18:39 ` Anatolij Gustschin
2018-08-07 6:56 Anatolij Gustschin
2018-08-07 15:32 ` Tom Rini
2016-02-06 18:18 Anatolij Gustschin
2016-02-08 20:45 ` Tom Rini
2014-10-31 0:02 Anatolij Gustschin
2014-11-04 20:00 ` Tom Rini
2014-08-21 17:17 Anatolij Gustschin
2014-08-25 12:35 ` Tom Rini
2013-03-29 13:26 Anatolij Gustschin
2013-04-01 16:30 ` Tom Rini
2013-01-14 22:28 Anatolij Gustschin
2013-01-14 22:40 ` Tom Rini
2012-11-14 13:52 Anatolij Gustschin
2012-11-19 19:59 ` Tom Rini
2012-11-08 12:39 Anatolij Gustschin
2012-11-08 15:07 ` Tom Rini
2012-10-05 23:06 Anatolij Gustschin
2012-10-08 16:09 ` Tom Rini
2012-09-21 23:10 Anatolij Gustschin
2012-09-22 0:21 ` Tom Rini
2012-09-22 0:22 ` Tom Rini
2012-09-01 12:44 Anatolij Gustschin
2012-09-01 22:46 ` Wolfgang Denk
2012-04-30 15:03 Anatolij Gustschin
2012-04-30 16:21 ` Wolfgang Denk
2012-04-16 16:42 Anatolij Gustschin
2012-04-16 21:00 ` Wolfgang Denk
2012-03-30 17:24 Anatolij Gustschin
2012-03-30 19:06 ` Wolfgang Denk
2011-12-20 21:35 Anatolij Gustschin
2011-12-20 22:15 ` Wolfgang Denk
2011-12-12 13:41 Anatolij Gustschin
2011-12-12 13:51 ` Wolfgang Denk
2011-12-09 16:36 Anatolij Gustschin
2011-12-10 21:46 ` Wolfgang Denk
2011-12-05 22:30 Anatolij Gustschin
2011-12-05 22:34 ` Wolfgang Denk
2011-11-27 19:28 Anatolij Gustschin
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=20180811191526.40c74448@crub \
--to=agust@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