From: Joel Stanley <joel@jms.id.au>
To: SoC Team <soc@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Andrew Jeffery <andrew@aj.id.au>,
linux-aspeed <linux-aspeed@lists.ozlabs.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] ARM: aspeed: devicetree changes for 5.11, round two
Date: Fri, 11 Dec 2020 11:09:39 +0000 [thread overview]
Message-ID: <CACPK8XfkZq51yKJUjyqgKD=R-WZiCR0J18GJBbo=tfMKMMddSQ@mail.gmail.com> (raw)
Message-ID: <20201211110939.Y2GW5E5EFWqFlhda8PEO2ihpoijt5pS8Ale-IwX592Q@z> (raw)
Hello Soc team,
Here are some late changes for the aspeed boards. Most are fixes, and
the addition of a new machine from Ampere.
(Arnd, I realised when sending the LPC clock fix that we had a few
others fixes, so he's a pull request instead)
The following changes since commit 5124cff93d99bbfe1efc8deb0c0b3604cb9a6659:
ARM: dts: aspeed: g220a: Fix some gpio (2020-12-11 21:28:02 +1030)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git
tags/aspeed-5.11-devicetree-2
for you to fetch changes up to 5124cff93d99bbfe1efc8deb0c0b3604cb9a6659:
ARM: dts: aspeed: g220a: Fix some gpio (2020-12-11 21:28:02 +1030)
----------------------------------------------------------------
ASPEED device tree updates for 5.11, round 2
- New machine
* Ampere's Mt Jade, an AST2500 BMC for Ampere's Altra reference
platform
- Fixes for eMMC, LPC clocking, and misc fixes for the g220a machine
----------------------------------------------------------------
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-12-11 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 11:09 Joel Stanley [this message]
2020-12-11 11:09 ` [GIT PULL] ARM: aspeed: devicetree changes for 5.11, round two Joel Stanley
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='CACPK8XfkZq51yKJUjyqgKD=R-WZiCR0J18GJBbo=tfMKMMddSQ@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=soc@kernel.org \
/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.