From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
openbmc@lists.ozlabs.org, Joel Stanley <joel@jms.id.au>
Subject: Re: [GIT PULL] FSI updates round 3 for 4.19
Date: Tue, 24 Jul 2018 08:00:59 +0200 [thread overview]
Message-ID: <20180724060059.GA15769@kroah.com> (raw)
In-Reply-To: <9071d5c82539c93f4a6cc8a76a11b14c3f507f09.camel@kernel.crashing.org>
On Tue, Jul 24, 2018 at 02:13:16PM +1000, Benjamin Herrenschmidt wrote:
> Hi Greg !
>
> This adds support for offloading the FSI low level bitbanging to the
> ColdFire coprocessor of the Aspeed SoCs. All the pre-requisites have
> already been merged, this is the final piece in the puzzle.
>
> This branch also pull gpio/ib-aspeed which is a topic branch already
> in gpio/for-next (and thus in next) whic contains pre-requisites.
>
> Finally, there's also a bug fix to the sbefifo driver for some
> inconsistent use of a mutex in the error handling code.
>
> Note: The oddball "origin" commit of that pull request comes from
> the fact that Linus Walleij gpio/ib-aspeed tree is ahead of mine,
> so pulling his branch pulled a bunch of already upstream other things
> in. As such, i had to base this pull request off a local merge. This
> shouldn't affect you at all, and allows the diffstat below to be
> correct.
>
> The bindings updates have been acked by Rob and the corresponding
> device-tree updates will be merged by Joel via the ARM SoC tree.
>
> Thanks !
> Ben.
>
> The following changes since commit d5e748ff2b996d83489ac76c072e8b99f9ecef13:
>
> Merge remote-tracking branch 'gpio/ib-aspeed' into upstream-ready (2018-07-23 15:21:39 +1000)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/benh/linux-fsi.git tags/fsi-updates-2018-07-24
Now pulled in and pushed out, thanks.
greg k-h
prev parent reply other threads:[~2018-07-24 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 4:13 Benjamin Herrenschmidt
2018-07-24 6:00 ` Greg Kroah-Hartman [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=20180724060059.GA15769@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benh@kernel.crashing.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@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
Powered by JetHome