From: Greg KH <gregkh@linuxfoundation.org>
To: Christopher Bostic <christopher.lee.bostic@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux@armlinux.org.uk,
Michael Turquette <mturquette@baylibre.com>,
geert+renesas@glider.be,
Open List OF Flattened dev tree bindings
<devicetree@vger.kernel.org>,
"Moderated list: ARM PORT" <linux-arm-kernel@lists.infradead.org>,
Joel Stanley <joel@jms.id.au>, Jeremy Kerr <jk@ozlabs.org>,
Linux open list <linux-kernel@vger.kernel.org>,
Andrew Jeffery <andrew@aj.id.au>,
Alistair Popple <alistair@popple.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Chris Bostic <cbostic@us.ibm.com>
Subject: Re: [PATCH v3 00/18] FSI device driver introduction
Date: Thu, 19 Jan 2017 10:11:05 +0100 [thread overview]
Message-ID: <20170119091105.GD29554@kroah.com> (raw)
In-Reply-To: <CAA0LjjVAJiF8yF8prE22Uz18A+EWnNAPis+4LydGRK2BVp6NSg@mail.gmail.com>
On Tue, Jan 17, 2017 at 04:00:41PM -0600, Christopher Bostic wrote:
> On Tue, Jan 17, 2017 at 1:42 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Jan 16, 2017 at 03:22:48PM -0600, christopher.lee.bostic@gmail.com wrote:
> >> From: Chris Bostic <cbostic@us.ibm.com>
> >
> > <snip>
> >
> > Only this, and patch 02/18 came through, did something get stuck on your
> > end?
> >
>
> Hi Greg,
>
> Yes had an issue with the server blocking send, investigating why.
It's still failing, I keep getting only the 00 email :(
next prev parent reply other threads:[~2017-01-19 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 21:22 [PATCH v3 00/18] FSI device driver introduction christopher.lee.bostic
2017-01-17 7:42 ` Greg KH
2017-01-17 22:00 ` Christopher Bostic
2017-01-19 9:11 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-17 22:02 christopher.lee.bostic
2017-01-19 0:30 christopher.lee.bostic
2017-02-01 16:53 Christopher Bostic
2017-02-01 17:01 Christopher Bostic
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=20170119091105.GD29554@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alistair@popple.id.au \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=cbostic@us.ibm.com \
--cc=christopher.lee.bostic@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@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