RE: RE: RE: RE: [PATCH v6 00/16] clk: exynos4/5: migrate to common clock framework
Mike Turquette wrote: [...] Yeah, I know. So if you want to add your ack on drivers/clk stuff for this series in samsung tree, please let me know. The patches are in pretty good shape. Please add my ack if you are able OK, I will. to rebase comfortably. But if rebasing causes you and your downstream users a lot of pain then don't do it. Yes it can be, but it can be handled easily because of no-changing codes. Note, please check Heiko's follow-up clk/samsung patches. http://comments.gmane.org/gmane.linux.kernel.samsung-soc/16817 I'm fine on that and if you're ok, I'd like to take that with this series. Thanks. - Kukjin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RE: RE: RE: [PATCH v6 00/16] clk: exynos4/5: migrate to common clock framework
Quoting Kukjin Kim (2013-03-21 16:26:24) Mike Turquette wrote: [...] Furthermore if I *had* agreed on the previous version it would still have been appropriate to put my Acked-by on those patches, which is clearly missing today. BTW, how about following? http://www.spinics.net/lists/arm-kernel/msg210266.html In my understanding, it should be your agreement, it cannot be 'ack' though. I had forgotten about that email from November. Still my ack should have been added. If necessary I'll be painfully explicit in the future Agreed. about adding my acked-by. It's a simple and good rule to follow. Yeah, I know. So if you want to add your ack on drivers/clk stuff for this series in samsung tree, please let me know. The patches are in pretty good shape. Please add my ack if you are able to rebase comfortably. But if rebasing causes you and your downstream users a lot of pain then don't do it. Regards, Mike Thanks, Mike. - Kukjin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: RE: RE: [PATCH v6 00/16] clk: exynos4/5: migrate to common clock framework
Mike Turquette wrote: [...] Furthermore if I *had* agreed on the previous version it would still have been appropriate to put my Acked-by on those patches, which is clearly missing today. BTW, how about following? http://www.spinics.net/lists/arm-kernel/msg210266.html In my understanding, it should be your agreement, it cannot be 'ack' though. I had forgotten about that email from November. Still my ack should have been added. If necessary I'll be painfully explicit in the future Agreed. about adding my acked-by. It's a simple and good rule to follow. Yeah, I know. So if you want to add your ack on drivers/clk stuff for this series in samsung tree, please let me know. Thanks, Mike. - Kukjin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RE: RE: [PATCH v6 00/16] clk: exynos4/5: migrate to common clock framework
Quoting Kukjin Kim (2013-03-19 21:50:05) Mike Turquette wrote: Quoting Kukjin Kim (2013-03-19 17:00:09) Mike Turquette wrote: [...] Thomas, Are you planning a V7 series which includes the clock alias bits from patch #1? Kukjin has already applied this series into the linux-samsung tree [0]. Thanks, Heiko. Mike, yes I did, as we discussed before. Since I missed in last window for v3.9, so I merged every common clock stuff for exynos into samsung tree in the early 3.9-rc time for v3.10. That really is too much code to go into drivers/clk without my ACK. I have not made much noise about this in the past but there has been more and more bonus code slipping into drivers/clk each merge window. Let's not do that any more. Hmm, I remember you already agreed on previous version, and I thought if any further codes are required, we could do it on top of that. http://lists.infradead.org/pipermail/linux-arm-kernel/2013- January/143429.html In the email you linked to my use of the word merged did not imply an ACK. I was asking about merging the two separate exynos4 and exynos5 ccf development efforts together. OK, I see. Furthermore if I *had* agreed on the previous version it would still have been appropriate to put my Acked-by on those patches, which is clearly missing today. BTW, how about following? http://www.spinics.net/lists/arm-kernel/msg210266.html In my understanding, it should be your agreement, it cannot be 'ack' though. I had forgotten about that email from November. Still my ack should have been added. If necessary I'll be painfully explicit in the future about adding my acked-by. It's a simple and good rule to follow. Thanks, Mike However, if you don't want current codes to be sent to upstream, let me know, but I don't think it would be better to us though. No, I am not asking you to revert/drop the patches, but I am using this as a public example. What's the 'public example'? As I linked, you already said 'sounds good to me' on my asking. - Kukjin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v6 00/16] clk: exynos4/5: migrate to common clock framework
Quoting Thomas Abraham (2013-02-18 00:21:10) Changes since v5: - Squashed several Exynos4 fixes patch from Tomasz Figa - Included support for Exynos5250 and Exynos5440, thus converting all Exynos4 and Exynos5 platforms to common clock framework. - Depends on the following patch series. - http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg15849.html - http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg15852.html Changes since v4: - Rebased to linux-3.8-rc1. Changes since v3: - Includes changes suggested by Tomasz Figa tomasz.f...@gmail.com This patch series migrates the Samsung Exynos4/5 SoC clock code to adopt the common clock framework. The use of Samsung specific clock structures has been removed and all board support code has been updated. imx-style of clock registration and lookup has been adopted for device tree based exynos4/5 platforms. Thomas, Are you planning a V7 series which includes the clock alias bits from patch #1? Regards, Mike -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v6 00/16] clk: exynos4/5: migrate to common clock framework
Am Dienstag, 19. März 2013, 19:49:38 schrieb Mike Turquette: Quoting Thomas Abraham (2013-02-18 00:21:10) Changes since v5: - Squashed several Exynos4 fixes patch from Tomasz Figa - Included support for Exynos5250 and Exynos5440, thus converting all Exynos4 and Exynos5 platforms to common clock framework. - Depends on the following patch series. - http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg15849 .html - http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg15852 .html Changes since v4: - Rebased to linux-3.8-rc1. Changes since v3: - Includes changes suggested by Tomasz Figa tomasz.f...@gmail.com This patch series migrates the Samsung Exynos4/5 SoC clock code to adopt the common clock framework. The use of Samsung specific clock structures has been removed and all board support code has been updated. imx-style of clock registration and lookup has been adopted for device tree based exynos4/5 platforms. Thomas, Are you planning a V7 series which includes the clock alias bits from patch #1? Kukjin has already applied this series into the linux-samsung tree [0]. The alias changes are available in the series clk: samsung: pm fixes and multiple aliases from last wednesday to on top, which you should hopefully also have received. This v2 series implements the changes discussed in the previous v1 clk: samsung: small fixes and enhancements from 2013-03-12, but didn't get any responses yet. Heiko [0] https://git.kernel.org/cgit/linux/kernel/git/kgene/linux-samsung.git/log/?h=next/clk-exynos -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH v6 00/16] clk: exynos4/5: migrate to common clock framework
Mike Turquette wrote: [...] Thomas, Are you planning a V7 series which includes the clock alias bits from patch #1? Kukjin has already applied this series into the linux-samsung tree [0]. Thanks, Heiko. Mike, yes I did, as we discussed before. Since I missed in last window for v3.9, so I merged every common clock stuff for exynos into samsung tree in the early 3.9-rc time for v3.10. That really is too much code to go into drivers/clk without my ACK. I have not made much noise about this in the past but there has been more and more bonus code slipping into drivers/clk each merge window. Let's not do that any more. Hmm, I remember you already agreed on previous version, and I thought if any further codes are required, we could do it on top of that. http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/143429.html However, if you don't want current codes to be sent to upstream, let me know, but I don't think it would be better to us though. Thanks. - Kukjin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RE: [PATCH v6 00/16] clk: exynos4/5: migrate to common clock framework
Quoting Kukjin Kim (2013-03-19 17:00:09) Mike Turquette wrote: [...] Thomas, Are you planning a V7 series which includes the clock alias bits from patch #1? Kukjin has already applied this series into the linux-samsung tree [0]. Thanks, Heiko. Mike, yes I did, as we discussed before. Since I missed in last window for v3.9, so I merged every common clock stuff for exynos into samsung tree in the early 3.9-rc time for v3.10. That really is too much code to go into drivers/clk without my ACK. I have not made much noise about this in the past but there has been more and more bonus code slipping into drivers/clk each merge window. Let's not do that any more. Hmm, I remember you already agreed on previous version, and I thought if any further codes are required, we could do it on top of that. http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/143429.html In the email you linked to my use of the word merged did not imply an ACK. I was asking about merging the two separate exynos4 and exynos5 ccf development efforts together. Furthermore if I *had* agreed on the previous version it would still have been appropriate to put my Acked-by on those patches, which is clearly missing today. However, if you don't want current codes to be sent to upstream, let me know, but I don't think it would be better to us though. No, I am not asking you to revert/drop the patches, but I am using this as a public example. Regards, Mike Thanks. - Kukjin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: RE: [PATCH v6 00/16] clk: exynos4/5: migrate to common clock framework
Mike Turquette wrote: Quoting Kukjin Kim (2013-03-19 17:00:09) Mike Turquette wrote: [...] Thomas, Are you planning a V7 series which includes the clock alias bits from patch #1? Kukjin has already applied this series into the linux-samsung tree [0]. Thanks, Heiko. Mike, yes I did, as we discussed before. Since I missed in last window for v3.9, so I merged every common clock stuff for exynos into samsung tree in the early 3.9-rc time for v3.10. That really is too much code to go into drivers/clk without my ACK. I have not made much noise about this in the past but there has been more and more bonus code slipping into drivers/clk each merge window. Let's not do that any more. Hmm, I remember you already agreed on previous version, and I thought if any further codes are required, we could do it on top of that. http://lists.infradead.org/pipermail/linux-arm-kernel/2013- January/143429.html In the email you linked to my use of the word merged did not imply an ACK. I was asking about merging the two separate exynos4 and exynos5 ccf development efforts together. OK, I see. Furthermore if I *had* agreed on the previous version it would still have been appropriate to put my Acked-by on those patches, which is clearly missing today. BTW, how about following? http://www.spinics.net/lists/arm-kernel/msg210266.html In my understanding, it should be your agreement, it cannot be 'ack' though. However, if you don't want current codes to be sent to upstream, let me know, but I don't think it would be better to us though. No, I am not asking you to revert/drop the patches, but I am using this as a public example. What's the 'public example'? As I linked, you already said 'sounds good to me' on my asking. - Kukjin -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v6 00/16] clk: exynos4/5: migrate to common clock framework
Changes since v5: - Squashed several Exynos4 fixes patch from Tomasz Figa - Included support for Exynos5250 and Exynos5440, thus converting all Exynos4 and Exynos5 platforms to common clock framework. - Depends on the following patch series. - http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg15849.html - http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg15852.html Changes since v4: - Rebased to linux-3.8-rc1. Changes since v3: - Includes changes suggested by Tomasz Figa tomasz.f...@gmail.com This patch series migrates the Samsung Exynos4/5 SoC clock code to adopt the common clock framework. The use of Samsung specific clock structures has been removed and all board support code has been updated. imx-style of clock registration and lookup has been adopted for device tree based exynos4/5 platforms. -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
