From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] Xilinx patches for v2019.04
Date: Thu, 24 Jan 2019 15:28:50 -0500 [thread overview]
Message-ID: <20190124202850.GM6906@bill-the-cat> (raw)
In-Reply-To: <a4a930ff-fdc2-66df-01ce-d2644425e709@monstr.eu>
On Thu, Jan 24, 2019 at 04:27:33PM +0100, Michal Simek wrote:
> Hi Tom,
>
> Here are several patches which I have in my queue.
> Buildman looks good and travis is also clear.
> https://travis-ci.org/michalsimek/u-boot/builds/483796826
>
> I have also sent several other patches to be able to finish transition
> to DM_I2C to reach the state that I can enable it for all boards and I2C
> will be described based on DT. This is not reviewed yet but hopefully
> this can go to this release too.
>
> In changes below there is nothing crucial. Boards which could be
> converted are converted to DM_I2C and OF_SEPARATE.
>
> Thanks,
> Michal
>
>
>
> The following changes since commit aff66f22d6eeb27c6329c0a3c1ebc52914c8affa:
>
> Merge tag 'mips-pull-2019-01-23' of git://git.denx.de/u-boot-mips
> (2019-01-23 17:24:31 -0500)
>
> are available in the git repository at:
>
>
> git://www.denx.de/git/u-boot-microblaze.git tags/xilinx-for-v2019.04
>
> for you to fetch changes up to 4efdbc88b79bd8bd3e285cd238e1942d669a7088:
>
> ARM: zynq: Convert Topic Miami to DM_I2C (2019-01-24 10:03:45 +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/20190124/f247d232/attachment.sig>
next prev parent reply other threads:[~2019-01-24 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 15:27 [U-Boot] [GIT PULL] Xilinx patches for v2019.04 Michal Simek
2019-01-24 20:28 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-17 9:05 Michal Simek
2019-04-18 16:19 ` Tom Rini
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=20190124202850.GM6906@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