From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: salvage lost CONFIG_REGULATOR
Date: Mon, 26 Jan 2015 03:57:47 +0000 [thread overview]
Message-ID: <20150126035742.GB1215@verge.net.au> (raw)
In-Reply-To: <87fvb2exr7.wl%kuninori.morimoto.gx@renesas.com>
On Mon, Jan 26, 2015 at 02:28:26AM +0000, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > I believe this problem is present in renesas-next-20150122-v3.19-rc1,
> > but not in renesas-devel-20150123-v3.19-rc5 due to the presence there of
> > the following in the latter:
> (snip)
> > It may have been better if the defconfig problem that Morimoto-san
> > mentions below had not gone into next for v3.20 while the change above
> > ended up being deferred for v3.21. But that is how things have
> > played out. And the result seems to be that Morimoto-san's patch
> > will resolve a regression that has been queued up for v3.20.
> >
> > With the above in mind I plan to queue up the change below
> > as a fix for v3.20.
>
> Thank you for your help.
> My patch is including below, because "make savedefconfig" did it
>
> -CONFIG_ARCH_SH73A0=y
> -CONFIG_SIMPLE_PM_BUS=y
> -CONFIG_RCAR_DMAC=y
>
> But, if these are based on merged branch (= Geert mentioned to it),
> I think I should send v2 (which includes REGURALOR only),
> otherwise, it will create other issues.
>
> My patch was based on renesas-devel-20150122-v3.19-rc5.
> but, can you show me best branch/tag for this issue ?
renesas-next-20150122-v3.19-rc1
The config items above would probably also be removed by savedefconfig
in renesas-next-20150122-v3.19-rc1 too. However, I think a minimal
approach is best for a fix: just removing REGURALOR as you suggest.
As you (now) know I have sent a patch to do that, which
I suppose crossed in-flight with your email.
prev parent reply other threads:[~2015-01-26 3:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 7:55 [PATCH] ARM: shmobile: salvage lost CONFIG_REGULATOR Kuninori Morimoto
2015-01-23 9:34 ` Geert Uytterhoeven
2015-01-26 1:19 ` Kuninori Morimoto
2015-01-26 1:24 ` Simon Horman
2015-01-26 2:26 ` Simon Horman
2015-01-26 2:28 ` Kuninori Morimoto
2015-01-26 3:57 ` Simon Horman [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=20150126035742.GB1215@verge.net.au \
--to=horms@verge.net.au \
--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;
as well as URLs for NNTP newsgroup(s).