From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 00/18] FSI device driver introduction
Date: Tue, 17 Jan 2017 08:42:43 +0100 [thread overview]
Message-ID: <20170117074243.GA20818@kroah.com> (raw)
In-Reply-To: <1484601768-98079-1-git-send-email-christopher.lee.bostic@gmail.com>
On Mon, Jan 16, 2017 at 03:22:48PM -0600, christopher.lee.bostic at 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?
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: christopher.lee.bostic@gmail.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
geert+renesas@glider.be, andrew@aj.id.au, alistair@popple.id.au,
mturquette@baylibre.com, linux@armlinux.org.uk,
Chris Bostic <cbostic@us.ibm.com>,
linux-kernel@vger.kernel.org, robh+dt@kernel.org, joel@jms.id.au,
benh@kernel.crashing.org, linux-arm-kernel@lists.infradead.org,
jk@ozlabs.org
Subject: Re: [PATCH v3 00/18] FSI device driver introduction
Date: Tue, 17 Jan 2017 08:42:43 +0100 [thread overview]
Message-ID: <20170117074243.GA20818@kroah.com> (raw)
In-Reply-To: <1484601768-98079-1-git-send-email-christopher.lee.bostic@gmail.com>
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?
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: christopher.lee.bostic@gmail.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
mturquette@baylibre.com, geert+renesas@glider.be,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
joel@jms.id.au, jk@ozlabs.org, linux-kernel@vger.kernel.org,
andrew@aj.id.au, alistair@popple.id.au, benh@kernel.crashing.org,
Chris Bostic <cbostic@us.ibm.com>
Subject: Re: [PATCH v3 00/18] FSI device driver introduction
Date: Tue, 17 Jan 2017 08:42:43 +0100 [thread overview]
Message-ID: <20170117074243.GA20818@kroah.com> (raw)
In-Reply-To: <1484601768-98079-1-git-send-email-christopher.lee.bostic@gmail.com>
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?
greg k-h
next prev parent reply other threads:[~2017-01-17 7:42 UTC|newest]
Thread overview: 21+ 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 at gmail.com
2017-01-16 21:22 ` christopher.lee.bostic
2017-01-16 21:22 ` christopher.lee.bostic-Re5JQEeQqe8AvxtiuMwx3w
2017-01-17 7:42 ` Greg KH [this message]
2017-01-17 7:42 ` Greg KH
2017-01-17 7:42 ` Greg KH
2017-01-17 22:00 ` Christopher Bostic
2017-01-17 22:00 ` Christopher Bostic
2017-01-17 22:00 ` Christopher Bostic
2017-01-19 9:11 ` Greg KH
2017-01-19 9:11 ` Greg KH
2017-01-19 9:11 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2017-01-17 22:02 christopher.lee.bostic at gmail.com
2017-01-17 22:02 ` christopher.lee.bostic
2017-01-19 0:30 christopher.lee.bostic at gmail.com
2017-01-19 0:30 ` christopher.lee.bostic
2017-02-01 16:53 Christopher Bostic
2017-02-01 16:53 ` Christopher Bostic
2017-02-01 16:53 ` Christopher Bostic
2017-02-01 17:01 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=20170117074243.GA20818@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.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.