From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/7] ARM: dts: Add Advantech board support
Date: Thu, 28 Jan 2016 14:29:02 +0800 [thread overview]
Message-ID: <20160128062902.GI9070@tiger> (raw)
In-Reply-To: <56A8F0FF.7020308@timesys.com>
On Wed, Jan 27, 2016 at 11:31:59AM -0500, Akshay Bhat wrote:
> I haven't seen any response from Shawn and seems like there has been
> no activity in his git tree for the last 5 weeks.
This is expected. In the past a few weeks, the tree was frozen to sort
out the materials we sent for merge window.
Shawn
> Was wondering if
> you would be able to provide further feedback (if any) and/or apply
> the patches. Appreciate your help.
prev parent reply other threads:[~2016-01-28 6:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 22:00 [PATCH v6 0/7] ARM: dts: Add Advantech board support Akshay Bhat
2015-12-23 22:00 ` [PATCH v6 1/7] of: Add vendor prefix for Advantech Corporation Akshay Bhat
2015-12-23 22:00 ` [PATCH v6 2/7] of: Add vendor prefix for General Electric Company Akshay Bhat
2015-12-23 22:00 ` [PATCH v6 3/7] ARM: dts: imx: Add Advantech BA-16 Qseven module Akshay Bhat
2016-01-28 5:41 ` Shawn Guo
2016-01-28 18:18 ` Akshay Bhat
2015-12-23 22:00 ` [PATCH v6 4/7] ARM: dts: imx: Add support for Advantech/GE Bx50v3 Akshay Bhat
2016-01-28 6:12 ` Shawn Guo
2016-01-28 18:26 ` Akshay Bhat
2015-12-23 22:00 ` [PATCH v6 5/7] ARM: dts: imx: Add support for Advantech/GE B450v3 Akshay Bhat
2016-01-28 6:14 ` Shawn Guo
2015-12-23 22:00 ` [PATCH v6 6/7] ARM: dts: imx: Add support for Advantech/GE B650v3 Akshay Bhat
2016-01-28 6:19 ` Shawn Guo
2016-01-28 18:54 ` Akshay Bhat
2015-12-23 22:00 ` [PATCH v6 7/7] ARM: dts: imx: Add support for Advantech/GE B850v3 Akshay Bhat
2016-01-28 6:26 ` Shawn Guo
2016-01-28 18:56 ` Akshay Bhat
2016-01-09 10:32 ` [PATCH v6 0/7] ARM: dts: Add Advantech board support Akshay Bhat
2016-01-27 16:31 ` Akshay Bhat
2016-01-28 6:29 ` Shawn Guo [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=20160128062902.GI9070@tiger \
--to=shawnguo@kernel.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 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).