public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: u-boot-staging
Date: Mon, 10 Jun 2019 09:42:48 -0400	[thread overview]
Message-ID: <20190610134248.GD7115@bill-the-cat> (raw)
In-Reply-To: <20190610132608.5f0bb4cf@crub>

On Mon, Jun 10, 2019 at 01:26:08PM +0200, Anatolij Gustschin wrote:
> Hi Tom,
> 
> please pull FEC driver fix for v2019.07.
> 
> Travis CI: https://travis-ci.org/vdsao/u-boot-video/builds/542223249
> 
> Thanks,
> Anatolij
> 
> The following changes since commit 38c2a8a00132b4dcc6a0bb5baf5146b9eb9eb2d2:
> 
>   Merge tag 'efi-2019-07-rc4' of git://git.denx.de/u-boot-efi (2019-06-02 18:19:45 -0400)
> 
> are available in the Git repository at:
> 
>   git://git.denx.de/u-boot-staging.git tags/fixes-for-2019.07
> 
> for you to fetch changes up to 023e2f900020991aedb3d57a257d46963b76221b:
> 
>   net: fec_mxc: not access reserved register on i.MX8 (2019-06-04 16:57:35 +0200)
> 
> ----------------------------------------------------------------
> - fix FEC exception/SERROR on i.MX8X
> 
> ----------------------------------------------------------------
> Peng Fan (1):
>       net: fec_mxc: not access reserved register on i.MX8
> 
>  drivers/net/fec_mxc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Since I'm expecting a PR from Stefano that includes the changes for
mx6sabre* to fit within SPL limits (and hoping he grabs the change to
make exceeding the limit a build error), shouldn't this just come from
him with all that?  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/20190610/c3eff34d/attachment.sig>

  reply	other threads:[~2019-06-10 13:42 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 11:26 [U-Boot] Pull request: u-boot-staging Anatolij Gustschin
2019-06-10 13:42 ` Tom Rini [this message]
2019-06-10 13:50   ` Anatolij Gustschin
  -- strict thread matches above, loose matches on Subject: below --
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-11 17:15 Anatolij Gustschin
2018-08-13  0:21 ` Tom Rini
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=20190610134248.GD7115@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