From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 repost] serial: sh-sci: Add device tree support for r8a7{778,740,3a4} and sh73a0
Date: Fri, 11 Jul 2014 17:44:51 -0700 [thread overview]
Message-ID: <20140712004451.GA9549@kroah.com> (raw)
In-Reply-To: <20140711091107.GA25710@verge.net.au>
On Fri, Jul 11, 2014 at 11:11:08AM +0200, Simon Horman wrote:
> Simply document new compat strings.
> There appears to be no need for a driver updates.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>
> --
> v2
> * Added r8a73a4, r8a7740 and sh73a0 support
>
> Repost to Greg KH.
>
> Greg, I am hoping to get the platform side of this change included in v3.16.
Isn't it a bit late for 3.16? I'll go add this to my 3.16 tree, as it's
just a .txt file, and leave the fighting over new code to the other
maintainers :)
thanks,
greg k-h
next prev parent reply other threads:[~2014-07-12 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 9:11 [PATCH v2 repost] serial: sh-sci: Add device tree support for r8a7{778,740,3a4} and sh73a0 Simon Horman
2014-07-12 0:44 ` Greg Kroah-Hartman [this message]
2014-07-12 6:50 ` Simon Horman
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=20140712004451.GA9549@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).