All of lore.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, Joel Stanley <joel@jms.id.au>
Subject: Re: [GIT PULL] FSI updates round 4 (last) for 4.19
Date: Fri, 27 Jul 2018 11:02:47 +0200	[thread overview]
Message-ID: <20180727090247.GC17942@kroah.com> (raw)
In-Reply-To: <81553544b2004efd42f256147d0d9f45df01df25.camel@kernel.crashing.org>

On Fri, Jul 27, 2018 at 10:10:57AM +1000, Benjamin Herrenschmidt wrote:
> Hi Greg !
> 
> This adds a few fixes for things reported since the last merge,
> and the latch batch of changes pending for FSI for 4.19.
> 
> That batch is a rather mechanical conversion of the misc devices
> into proper char devices.
> 
> The misc devices were ill suited, the minor space for them is
> limited and we can have a lot of chips in a system creating FSI
> devices.
> 
> This also allows us to better control (and fix) object lifetime
> getting rid of the bad devm_kzalloc() of the structures containing
> the devices etc...
> 
> Finally, we add a chardev to the core FSI that provides raw CFAM
> access to FSI slaves as a replacement for the current "raw" binary
> sysfs file which will be ultimately deprecated and removed.
> 
> Thanks !
> Ben.
> 
> The following changes since commit 0a213777d1dd879092225a7aa847b6e9b3a1c267:
> 
>   fsi: Add support for device-tree provided chip IDs (2018-07-23 16:27:32 +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-27

Pulled in and pushed out, thanks.

greg k-h

      reply	other threads:[~2018-07-27  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27  0:10 [GIT PULL] FSI updates round 4 (last) for 4.19 Benjamin Herrenschmidt
2018-07-27  9:02 ` 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=20180727090247.GC17942@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.