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: [PULL] u-boot-atmel-fixes-2021.01-b
Date: Sat, 12 Dec 2020 09:58:38 -0500	[thread overview]
Message-ID: <20201212145838.GE32272@bill-the-cat> (raw)
In-Reply-To: <be110e13-ec05-a569-e2aa-dfce1655a8ea@microchip.com>

On Fri, Dec 11, 2020 at 04:36:41PM +0000, Eugen.Hristev at microchip.com wrote:

> Hello Tom,
> 
> Please pull tag u-boot-atmel-fixes-2021.01-b , the second set of atmel
> fixes for 2021.01 cycle.
> 
> This set includes very important fixes for: MMC booting on several 
> boards, drive strength on sam9x60ek mmc lines, compile issues for 
> timer.c old driver, removal of unwanted access to sam9x60 bit for 
> oscillator bypass mode, and eeproms read on sama5d2_icp.
> 
> Thanks !
> Eugen
> 
> The following changes since commit 1ae955e3a58f46918ef99b0b6c562967ba1bf39e:
> 
>    Prepare v2021.01-rc2 (2020-11-09 17:20:05 -0500)
> 
> are available in the Git repository at:
> 
>    https://gitlab.denx.de/u-boot/custodians/u-boot-atmel.git 
> tags/u-boot-atmel-fixes-2021.01-b
> 
> for you to fetch changes up to bb5eedbc7fbddc7849bb10a239facac29b615c1c:
> 
>    ARM: dts: at91: sama5d2_icp: fix i2c eeprom compatible (2020-12-11 
> 17:47:21 +0200)
> 

Applied to u-boot/master, 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/20201212/94cd2b31/attachment.sig>

      reply	other threads:[~2020-12-12 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 16:36 [PULL] u-boot-atmel-fixes-2021.01-b Eugen.Hristev at microchip.com
2020-12-12 14:58 ` Tom Rini [this message]

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=20201212145838.GE32272@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