openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	openbmc@lists.ozlabs.org
Subject: Re: [GIT PULL]  FSI updates
Date: Tue, 12 Jun 2018 20:23:17 +1000	[thread overview]
Message-ID: <b91d8e9b0df0600a5fd00ae0e00067d366bcc551.camel@kernel.crashing.org> (raw)
In-Reply-To: <20180612062059.GA26240@kroah.com>

On Tue, 2018-06-12 at 08:20 +0200, Greg Kroah-Hartman wrote:
> On Tue, Jun 12, 2018 at 02:14:25PM +1000, Benjamin Herrenschmidt wrote:
> > Hi Greg !
> > 
> > There are a first round of updates of the FSI stack, aiming at reducing/removing
> > the 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).
> > 
> > [ Apologies if I got part of the process wrong, I haven't
> >   sent a pull request in years ;-) ]
> 
> So, these are all for 4.19-rc1, right?  Not bugfixes for 4.18-final?

The earlier the better as it reduces the diff with openbmc kernel tree
(with the goal of going down to 0) and simplify merging further new
stuff that depends on this. We are the only users of drivers/fsi so the
risk is for now at least nul. That said if you prefer queuing that up
for 4.19, that's ok (the patches were posted a little while ago, this
is just putting them in a git repo, nothing new since).

> > 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 
> 
> I need a signed tag to pull from, not just a git tree, otherwise I don't
> know that you really sent me what you think you sent me :)
> 
> Can you fix that up, and tell me where you want this to go and then I
> can take it after 4.18-rc1 is out.

Ah ok, I haven't done signed tags yet :-) Linus didn't require them
back in the day for kernel.org hosted trees. I'll look into it
tomorrow.

Cheers,
Ben.

> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2018-06-12 10:23 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 [this message]
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

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=b91d8e9b0df0600a5fd00ae0e00067d366bcc551.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=gregkh@linuxfoundation.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).