public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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] FSI updates round 2 for 4.19
Date: Thu, 12 Jul 2018 08:42:58 +0200	[thread overview]
Message-ID: <20180712064258.GA25229@kroah.com> (raw)
In-Reply-To: <6b3728c37095b54666827d61d0540dddf0187a80.camel@kernel.crashing.org>

On Thu, Jul 12, 2018 at 01:03:44PM +1000, Benjamin Herrenschmidt wrote:
> Hi Greg !
> 
> This is the second round of updates of the FSI stack.
> 
> These comprise of:
> 
>  - Some build fixes detected with COMPILE_TEST when
> used on "other" archs
> 
>  - Sparse warning fixes
> 
>  - Some object lifetime fixes
> 
>  - A new feature to control some of the protocol delays
> 
>  - Overheaul of the "SCOM" driver used to access the POWER
> processor internal SCOM bus.
> 
>  - Preparatory work for the new ColdFire coprocessor based FSI master
> work which, along some other newer work is still going through the last
> few rounds of polish and DT bindings reviews.
> 
> The following changes since commit 9f4a8a2d7f9d71093f41c4bb0ef8707e8145bad3:
> 
>   fsi/sbefifo: Add driver for the SBE FIFO (2018-06-12 14:05: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-12

Pulled and pushed out now, thanks.

greg k-h

      reply	other threads:[~2018-07-12  6:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12  3:03 [GIT PULL] FSI updates round 2 for 4.19 Benjamin Herrenschmidt
2018-07-12  6:42 ` 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=20180712064258.GA25229@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