[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFRkauCft5p4P_LkZVLde62Yh03p-_2hNPm6wEct5XSeg-p0Bg@mail.gmail.com>
Date: Tue, 8 Oct 2019 18:53:22 +0800
From: Axel Lin <axel.lin@...ics.com>
To: Mark Brown <broonie@...nel.org>
Cc: Steve Twiss <stwiss.opensource@...semi.com>,
Support Opensource <support.opensource@...semi.com>,
Liam Girdwood <lgirdwood@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Adam Thomson <Adam.Thomson.Opensource@...semi.com>
Subject: Re: [RESEND][PATCH 2/2] regulator: da9062: Simplify
da9062_buck_set_mode for BUCK_MODE_MANUAL case
Mark Brown <broonie@...nel.org> 於 2019年10月8日 週二 下午6:51寫道:
>
> On Tue, Oct 08, 2019 at 06:48:15PM +0800, Axel Lin wrote:
> > Mark Brown <broonie@...nel.org> 於 2019年10月8日 週二 下午6:44寫道:
>
> > > It doesn't seem to apply against current code.
>
> > I just test apply it and It looks fine to be applied by linux-next tree.
> > Or which branch of regulator tree should I generate the patch?
>
> Well, I queued it for 5.5. I've not seen if it's got dependencies
> against 5.4 yet but you chased me so...
Ok, I see the problem.
commit a72865f05782 ("regulator: da9062: fix suspend_enable/disable
preparation") is in for-5.4 branch
but not in for-5.5 branch. So it does not apply to for-5.5 branch.
But if I generate the patch on for-5.5 branch, I think you will get
conflict when merge for-5.4 and for-5.5 to for-next.
Powered by blists - more mailing lists