From: Paul Mundt <lethal@linux-sh.org>
To: Simon Horman <horms@verge.net.au>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Bastian Hecht <hechtb@gmail.com>,
linux-sh@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v3 1/3] serial: sh-sci: Add OF support
Date: Wed, 27 Feb 2013 18:34:40 +0900 [thread overview]
Message-ID: <20130227093439.GE30395@linux-sh.org> (raw)
In-Reply-To: <20130227090456.GA7936@verge.net.au>
On Wed, Feb 27, 2013 at 06:04:57PM +0900, Simon Horman wrote:
> On Wed, Feb 27, 2013 at 05:26:57PM +0900, Magnus Damm wrote:
> > My personal preference would be that you (Paul) merge this patch by yourself:
> > [PATCH v3 1/3] serial: sh-sci: Add OF support
> >
> > I believe we can deal with the SoC bits easily afterwards. Simon may
> > however prefer to deal with it differently.
> >
> > Simon, how do you prefer to handle merge of DT support for the SCIF driver?
>
> I am fairly ambivalent.
>
> If Paul could merge this patch upstream in the v3.9-rc1~rc3 time frame
> then I can queue up the SoC portions for v3.10.
>
> Or alternatively I can queue up all three patches for v3.10.
> Either way the outcome should be much the same.
Waiting an entire kernel version to throw some arbitrary dts file updates
in seems a bit absurd, but I'll let you handle it however you like. I
haven't sent out my SH updates to Linus yet, but plan to do so by -rc2
(there isn't really that much to begin with, most of it has gone through
other trees), so in light of this I will throw the sh-sci OF patch in to
my queue directly then.
next prev parent reply other threads:[~2013-02-27 9:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 17:03 [PATCH v3 1/3] serial: sh-sci: Add OF support Bastian Hecht
2013-02-26 17:03 ` [PATCH v3 2/3] ARM: mach-shmobile: r8a7740: Add DT names to clock list Bastian Hecht
2013-03-01 9:42 ` Simon Horman
2013-02-26 17:03 ` [PATCH v3 3/3] ARM: mach-shmobile: r8a7740: Setup the serial devices using DT Bastian Hecht
2013-03-01 9:42 ` Simon Horman
2013-03-01 16:21 ` Bastian Hecht
2013-03-02 1:31 ` Simon Horman
2013-03-04 12:48 ` Magnus Damm
2013-03-04 13:33 ` Guennadi Liakhovetski
2013-03-05 3:27 ` Simon Horman
2013-03-05 6:52 ` Guennadi Liakhovetski
2013-03-05 7:04 ` Simon Horman
2013-03-04 15:44 ` Bastian Hecht
2013-03-05 3:36 ` Simon Horman
2013-02-27 8:07 ` [PATCH v3 1/3] serial: sh-sci: Add OF support Paul Mundt
2013-02-27 8:11 ` Magnus Damm
2013-02-27 8:19 ` Paul Mundt
2013-02-27 8:26 ` Magnus Damm
2013-02-27 9:04 ` Simon Horman
2013-02-27 9:34 ` Paul Mundt [this message]
2013-02-28 19:20 ` Bastian Hecht
2013-03-01 0: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=20130227093439.GE30395@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=hechtb@gmail.com \
--cc=horms@verge.net.au \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).