From: Arnd Bergmann <arnd@kernel.org>
To: SoC Team <soc@kernel.org>, Joel Stanley <joel@jms.id.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
"Chia-Wei, Wang" <chiawei_wang@aspeedtech.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Andrew Jeffery <andrew@aj.id.au>,
Corey Minyard <cminyard@mvista.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-aspeed <linux-aspeed@lists.ozlabs.org>
Subject: Re: [GIT PULL] ARM: aspeed: lpc changes for 5.13
Date: Fri, 9 Apr 2021 09:18:20 +0200 [thread overview]
Message-ID: <161795267844.1750068.14862109207368145425.b4-ty@arndb.de> (raw)
In-Reply-To: <CACPK8Xcb12LsVr7CUaXXjQskKbVjb7x+jgueG1Hik-kBPWtDSg@mail.gmail.com>
From: Arnd Bergmann <arnd@arndb.de>
On Fri, 9 Apr 2021 06:29:52 +0000, Joel Stanley wrote:
> This is a pull request containing a slightly messy device tree and
> associated driver changes for the ASPEED systems. It corrects some
> design decisions made when first mainlining support for the BMC
> devices on the LPC bus that have stopped us from being able to write
> drivers for eg. KCS.
>
> Andrew has worked with Chai-Wei from ASPEED on this process. These set
> of changes have acks from the maintainers, and allow Andrew to go
> ahead with fixing the KCS drivers in the future. The branch should
> apply with no conflicts no matter which order it is merged.
>
> [...]
Merged into arm/drivers, thanks!
merge commit: d60f314b93b637e9721c406f5a61cf2157e59b48
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-04-09 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 6:29 [GIT PULL] ARM: aspeed: lpc changes for 5.13 Joel Stanley
2021-04-09 7:18 ` Arnd Bergmann [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=161795267844.1750068.14862109207368145425.b4-ty@arndb.de \
--to=arnd@kernel.org \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=chiawei_wang@aspeedtech.com \
--cc=cminyard@mvista.com \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--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 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).