public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: Please add the fsi tree
Date: Fri, 22 Jun 2018 11:53:50 +1000	[thread overview]
Message-ID: <c304c6e08d7baa6e725c2634ea94b7fa326edd5a.camel@kernel.crashing.org> (raw)

Hi Stephen !

Please add the fsi tree at

https://git.kernel.org/pub/scm/linux/kernel/git/benh/linux-fsi.git (master)

To linux-next. It contains the changes that I will send to Greg KH to the FSI
subsystem used by the service processor to communicate with IBM Power chips
(and eventually S390 as well).

Commits in there are intende to be merged via Greg's tree. Signed tags in
there have already been the subject of pull requests to Greg.

Thanks !

Cheers,
Ben.

             reply	other threads:[~2018-06-22  1:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  1:53 Benjamin Herrenschmidt [this message]
2018-06-22  3:10 ` linux-next: Please add the fsi tree Stephen Rothwell

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=c304c6e08d7baa6e725c2634ea94b7fa326edd5a.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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