SUPERH platform development
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh-pfc: r8a7779: fixup INDTx address
Date: Tue, 05 Mar 2013 04:11:50 +0000	[thread overview]
Message-ID: <20130305041149.GC14275@linux-sh.org> (raw)
In-Reply-To: <87lia3pn80.wl%kuninori.morimoto.gx@renesas.com>

On Tue, Mar 05, 2013 at 12:18:52PM +0900, Simon Horman wrote:
> [ Cc: Linus Walleij ]
> 
> Hi Linus, Hi Paul, Hi Laurent,
> 
> I'm a little unsure how everyone would like to handle
> drivers/pinctrl/sh-pfc/ updates.
> 
> I'm happy to create a pfc branch and send pull requests to Linus.
> Or for Paul to handle things. Or for Laurent to handle things.
> Or for other suggestions.
> 
> To confuse things, I believe there are a batch of PFC changes that
> will make sense to take through the arm-soc tree due to dependencies.
> 
It doesn't particularly matter to me where the updates go, so long as
everyone is kept aware of what changes are being made before they're
silently merged somewhere.

Stuff like this falls more in to the obvious bugfix category, and is
probably fine for arm-soc, given that it's largely SoC-specific. I would
prefer if the sh-pfc core stuff remain independent of arm-soc however,
but it's not terribly important whether I merge it or Linus does.

  parent reply	other threads:[~2013-03-05  4:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  8:45 [PATCH] sh-pfc: r8a7779: fixup INDTx address Kuninori Morimoto
2013-03-05  3:18 ` Simon Horman
2013-03-05  4:11 ` Paul Mundt [this message]
2013-03-05  4:14 ` Kuninori Morimoto
2013-03-05  8:58 ` Simon Horman
2013-03-05 17:51 ` phil.edworthy
2013-03-06  0:39 ` Laurent Pinchart
2013-03-06  0:51 ` Kuninori Morimoto
2013-03-06  1:58 ` Simon Horman
2013-03-06  1:59 ` Simon Horman
2013-03-06  7:18 ` phil.edworthy
2013-03-06  7:29 ` Simon Horman
2013-03-06  7:53 ` Magnus Damm
2013-03-06  7:58 ` Kuninori Morimoto
2013-03-06  8:50 ` phil.edworthy
2013-03-06  8:54 ` Magnus Damm

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=20130305041149.GC14275@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@vger.kernel.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