All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PULL] u-boot-atmel-fixes-2020.07-a
Date: Thu, 4 Jun 2020 11:05:06 -0400	[thread overview]
Message-ID: <20200604150506.GF32287@bill-the-cat> (raw)
In-Reply-To: <a3c76d8b-7001-d875-290d-158ab7b3fd5d@microchip.com>

On Thu, Jun 04, 2020 at 02:01:02PM +0000, Eugen.Hristev at microchip.com wrote:

> Hello Tom,
> 
> Please pull tag u-boot-atmel-fixes-2020.07-a , the first set of changes 
> for the 2020.07 cycle.
> 
> This set includes just two small commits that fix a build warning and 
> add a missing serial node.
> 
> Thanks !
> Eugen
> 
> 
> The following changes since commit dd2c676a659a03daeef31d1221da2edff009d426:
> 
>    Prepare v2020.07-rc1 (2020-04-28 15:55:57 -0400)
> 
> are available in the Git repository at:
> 
>    https://gitlab.denx.de/u-boot/custodians/u-boot-atmel.git 
> tags/u-boot-atmel-fixes-2020.07-a
> 
> for you to fetch changes up to d32cbefc8ac82bd0206f806efb07df82c4b92d5b:
> 
>    ARM: dts: sama5d2: Add uart4 definition (2020-05-18 15:00:20 +0300)
> 

Applied to u-boot/master, thanks!

But please note that building for all of "sama5" gives a ton of device
tree warnings, can you please look in to them?  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200604/435ae138/attachment.sig>

  reply	other threads:[~2020-06-04 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 14:01 [PULL] u-boot-atmel-fixes-2020.07-a Eugen.Hristev at microchip.com
2020-06-04 15:05 ` Tom Rini [this message]
2020-06-04 15:26   ` Eugen.Hristev at microchip.com
2020-06-04 16:55     ` 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=20200604150506.GF32287@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.