From: Joel Stanley <joel@jms.id.au>
To: arm <arm@kernel.org>
Cc: Andrew Jeffery <andrew@aj.id.au>,
linux-aspeed@lists.ozlabs.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] ARM: aspeed: defconfig changes for 5.3
Date: Sat, 22 Jun 2019 07:58:46 +0000 [thread overview]
Message-ID: <CACPK8XfL-U-BeynGQNBp5rPiv1gzD=7DVzyvrgtoL3njU1Kr_A@mail.gmail.com> (raw)
Hi ARM maintainers,
Here are some defconfig updates for the ASPEED machines. I haven't
sent one for a while, so there's a nice collection of drivers to add.
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git \
tags/aspeed-5.3-defconfig
for you to fetch changes up to 2d8bf3404bb0e65dffb7326f7fb6e96fa3cee418:
ARM: configs: multi_v5: Add more ASPEED devices (2019-06-22 17:12:17 +0930)
----------------------------------------------------------------
ASPEED device tree updates for 5.3
Add new drivers to the ASPEED G4 and G5 defconfigs, and to the armv5
multi defconfig.
----------------------------------------------------------------
Joel Stanley (2):
ARM: configs: aspeed: Add new drivers
ARM: configs: multi_v5: Add more ASPEED devices
arch/arm/configs/aspeed_g4_defconfig | 10 ++++++++--
arch/arm/configs/aspeed_g5_defconfig | 14 ++++++++++++--
arch/arm/configs/multi_v5_defconfig | 8 ++++++++
3 files changed, 28 insertions(+), 4 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-06-22 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 7:58 Joel Stanley [this message]
2019-06-25 12:21 ` [GIT PULL] ARM: aspeed: defconfig changes for 5.3 Olof Johansson
2019-06-25 13:18 ` Olof Johansson
2019-06-26 2:03 ` Joel Stanley
2019-06-27 2:18 ` Olof Johansson
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='CACPK8XfL-U-BeynGQNBp5rPiv1gzD=7DVzyvrgtoL3njU1Kr_A@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).