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>
Subject: Re: [GIT PULL] FSI fixes for 4.20
Date: Mon, 26 Nov 2018 08:03:48 +0100 [thread overview]
Message-ID: <20181126070348.GC9680@kroah.com> (raw)
In-Reply-To: <b0960d55bb1895253caefe942f8065ac84213267.camel@kernel.crashing.org>
On Mon, Nov 26, 2018 at 10:37:08AM +1100, Benjamin Herrenschmidt wrote:
> Hi Greg !
>
> Here are two very minor fixes for FSI. One from Arnd is a Kconfig fixup
> and has been rusting away in my tree for a while (I had forgotten about
> it). The other one just removes a duplicate #include, courtesy of
> Brajeswar Ghosh.
>
> The following changes since commit 2e6e902d185027f8e3cb8b7305238f7e35d6a436:
>
> Linux 4.20-rc4 (2018-11-25 14:19:31 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/benh/linux-fsi.git tags/fsi-updates-2018-11-26
Now pulled, thanks.
greg k-h
prev parent reply other threads:[~2018-11-26 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 23:37 [GIT PULL] FSI fixes for 4.20 Benjamin Herrenschmidt
2018-11-26 7: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=20181126070348.GC9680@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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).