Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1396211 > unrolled thread
| Started by | Stephen Boyd <sboyd@codeaurora.org> |
|---|---|
| First post | 2016-05-07 03:00 +0200 |
| Last post | 2016-05-10 09:50 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v3 3/4] mfd: arizona: Switch to using clock driver for 32k clock Stephen Boyd <sboyd@codeaurora.org> - 2016-05-07 03:00 +0200
Re: [PATCH v3 3/4] mfd: arizona: Switch to using clock driver for 32k clock Lee Jones <lee.jones@linaro.org> - 2016-05-09 09:50 +0200
Re: [PATCH v3 3/4] mfd: arizona: Switch to using clock driver for 32k clock Stephen Boyd <sboyd@codeaurora.org> - 2016-05-09 21:40 +0200
Re: [PATCH v3 3/4] mfd: arizona: Switch to using clock driver for 32k clock Lee Jones <lee.jones@linaro.org> - 2016-05-10 09:50 +0200
| From | Stephen Boyd <sboyd@codeaurora.org> |
|---|---|
| Date | 2016-05-07 03:00 +0200 |
| Subject | Re: [PATCH v3 3/4] mfd: arizona: Switch to using clock driver for 32k clock |
| Message-ID | <rvYL8-82X-5@gated-at.bofh.it> |
On 01/08, Charles Keepax wrote: > Now we have a clock driver that can control the 32k clock use this > rather than directly controlling the 32k clock from the MFD device. > > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com> > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
[toc] | [next] | [standalone]
| From | Lee Jones <lee.jones@linaro.org> |
|---|---|
| Date | 2016-05-09 09:50 +0200 |
| Message-ID | <rwO71-yr-47@gated-at.bofh.it> |
| In reply to | #1396211 |
On Fri, 06 May 2016, Stephen Boyd wrote: > On 01/08, Charles Keepax wrote: > > Now we have a clock driver that can control the 32k clock use this > > rather than directly controlling the 32k clock from the MFD device. > > > > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com> > > --- > > Applied to clk-next If you're going to take the set though the clk tree, don't forget to sent out a pull-request of the immutable branch you created. If you're not happy to do that, drop the patch and I'll happily oblige. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog
[toc] | [prev] | [next] | [standalone]
| From | Stephen Boyd <sboyd@codeaurora.org> |
|---|---|
| Date | 2016-05-09 21:40 +0200 |
| Message-ID | <rwZc6-3qZ-27@gated-at.bofh.it> |
| In reply to | #1396788 |
On 05/09, Lee Jones wrote: > On Fri, 06 May 2016, Stephen Boyd wrote: > > > On 01/08, Charles Keepax wrote: > > > Now we have a clock driver that can control the 32k clock use this > > > rather than directly controlling the 32k clock from the MFD device. > > > > > > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com> > > > --- > > > > Applied to clk-next > > If you're going to take the set though the clk tree, don't forget to > sent out a pull-request of the immutable branch you created. If > you're not happy to do that, drop the patch and I'll happily oblige. > Oh sorry, I got confused. I thought you acked this mfd patch so I could take it through the clk tree but it seems you acked them so you could apply it later without re-reviewing it? Either way, I'm going to drop these patches for now and wait for a v4 because Charles has suggested there are some more issues to work out. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
[toc] | [prev] | [next] | [standalone]
| From | Lee Jones <lee.jones@linaro.org> |
|---|---|
| Date | 2016-05-10 09:50 +0200 |
| Message-ID | <rxaAy-6l0-27@gated-at.bofh.it> |
| In reply to | #1397271 |
On Mon, 09 May 2016, Stephen Boyd wrote: > On 05/09, Lee Jones wrote: > > On Fri, 06 May 2016, Stephen Boyd wrote: > > > > > On 01/08, Charles Keepax wrote: > > > > Now we have a clock driver that can control the 32k clock use this > > > > rather than directly controlling the 32k clock from the MFD device. > > > > > > > > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com> > > > > --- > > > > > > Applied to clk-next > > > > If you're going to take the set though the clk tree, don't forget to > > sent out a pull-request of the immutable branch you created. If > > you're not happy to do that, drop the patch and I'll happily oblige. > > > > Oh sorry, I got confused. I thought you acked this mfd patch so I could > take it through the clk tree but it seems you acked them so you > could apply it later without re-reviewing it? Right, that's what I mean by "for my own reference". Since MFD is more often than not the central/parent device, it's usually easier to tunnel patch sets through the MFD, and I will always sent out a pull-requests out to the other maintainers concerned in order to prevent merge conflicts for Linus. > Either way, I'm going to drop these patches for now and wait for > a v4 because Charles has suggested there are some more issues to > work out. Sure. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web