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
Subject: Re: [GIT PULL v2] FSI updates for 4.17
Date: Sat, 7 Jul 2018 17:03:12 +0200 [thread overview]
Message-ID: <20180707150312.GA410@kroah.com> (raw)
In-Reply-To: <5c7f9044fefed8bc0e4ca5688801ffa379f38f62.camel@kernel.crashing.org>
On Tue, Jun 12, 2018 at 08:54:39PM +1000, Benjamin Herrenschmidt wrote:
> Hi Greg !
>
> There are a first round of updates of the FSI stack, aiming at reducing/removing
> he gap with the OpenBMC tree and a first step in getting dependent drivers
> upstream.
>
> These changes significantly improve the FSI bitbanging driver performance
> and reliability, and add the new "sbefifo" driver for communicating with
> the POWER9 Self Boot Engine (which will be needed for some upcoming
> additional drivers).
>
> These were posted to the list as patches a couple of weeks ago and were
> prior to that tested in the OpenBMC tree and CI. Some subsequent driver
> work depends on some of these, so merging early is probably the best.
>
> The following changes since commit 8efcf34a263965e471e3999904f94d1f6799d42a:
>
> Merge tag 'armsoc-late' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2018-06-11 18:19:45 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/benh/linux-fsi.git tags/fsi-updates-2018-06-12
Sorry for the delay, now merged.
greg k-h
prev parent reply other threads:[~2018-07-07 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 4:14 [GIT PULL] FSI updates Benjamin Herrenschmidt
2018-06-12 6:20 ` Greg Kroah-Hartman
2018-06-12 10:23 ` Benjamin Herrenschmidt
2018-06-12 10:54 ` [GIT PULL v2] FSI updates for 4.17 Benjamin Herrenschmidt
2018-06-12 11:18 ` Greg Kroah-Hartman
2018-06-12 11:25 ` Benjamin Herrenschmidt
2018-06-12 11:44 ` Greg Kroah-Hartman
2018-06-12 12:40 ` Benjamin Herrenschmidt
2018-07-07 15:03 ` 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=20180707150312.GA410@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benh@kernel.crashing.org \
--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;
as well as URLs for NNTP newsgroup(s).