From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: ION DTS changes for HiKey in -next
Date: Thu, 7 Jan 2016 21:02:14 -0800 [thread overview]
Message-ID: <20160108050214.GD30293@kroah.com> (raw)
In-Reply-To: <20160107173744.GJ6588@sirena.org.uk>
On Thu, Jan 07, 2016 at 05:37:44PM +0000, Mark Brown wrote:
> Hi Greg,
>
> I was just looking at DTs in -next and noticed that there is a patch
> 59dfafd03fc (arm64: dts: Add dts files to enable ION on Hi6220 SoC)
> which adds at DT doing something for ION. Are we sure this should be
> going into the main production DT? The bindings haven't been reviewed
> as far as I can tell, the matching driver is only in staging and hasn't
> been posted upstream.
Isn't "staging" upstream enough for this? :)
If not, let me know and I'll be glad to drop this patch, it was on the
list for a while with no objections.
thanks,
greg k-h
next prev parent reply other threads:[~2016-01-08 5:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 17:37 ION DTS changes for HiKey in -next Mark Brown
2016-01-08 5:02 ` Greg Kroah-Hartman [this message]
2016-01-08 12:44 ` Mark Brown
2016-01-08 13:55 ` Mark Rutland
2016-01-08 18:14 ` Laura Abbott
2016-01-09 5:05 ` Greg Kroah-Hartman
2016-01-11 15:18 ` Laura Abbott
2016-01-11 10:09 ` Mark Rutland
2016-01-09 5:05 ` Greg Kroah-Hartman
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=20160108050214.GD30293@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 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).