| Message ID | 20220715045936.xsrxduwit4beijzi@vireshk-i7 |
|---|---|
| State | New |
| Headers | show |
| Series | [GIT,PULL] cpufreq/arm fixes for 5.19-rc7 | expand |
On Fri, Jul 15, 2022 at 6:59 AM Viresh Kumar <viresh.kumar@linaro.org> wrote: > > The following changes since commit be4b61ec45b3efe5e9077525fc92d544305eb2a6: > > cpufreq: Add MT8186 to cpufreq-dt-platdev blocklist (2022-06-28 13:34:56 +0530) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git tags/cpufreq-arm-fixes-5.19-rc7 > > for you to fetch changes up to d2394860b45c3c1484e4b0a5d09909a1e3f6569e: > > cpufreq: mediatek: Handle sram regulator probe deferral (2022-07-13 16:51:32 +0530) > > ---------------------------------------------------------------- > cpufreq arm fixes for 5.19-rc6 > > - mediatek: Handle sram regulator probe deferral > > ---------------------------------------------------------------- > AngeloGioacchino Del Regno (1): > cpufreq: mediatek: Handle sram regulator probe deferral > > drivers/cpufreq/mediatek-cpufreq.c | 8 ++++++-- > 1 file changed, 6 insertions(+), 2 deletions(-) Pulled and pushed out, but I would appreciate getting pull requests somewhat earlier before the -rc I'm supposed to be pushing them for. Thanks!
On 15-07-22, 14:00, Rafael J. Wysocki wrote: > Pulled and pushed out, but I would appreciate getting pull requests > somewhat earlier before the -rc I'm supposed to be pushing them for. Yeah, that's what I try too. But this time the patch itself came in on July 13th and I sent the pull request on July 15th. I mentioned -rc7 as that was the next rc in line, but it was actually fine for this to be applied after rc7 too, before the 5.19 release though. Should I send the pull request (and tag) without mentioning the rc number in future ?
On Mon, Jul 18, 2022 at 3:41 AM Viresh Kumar <viresh.kumar@linaro.org> wrote: > > On 15-07-22, 14:00, Rafael J. Wysocki wrote: > > Pulled and pushed out, but I would appreciate getting pull requests > > somewhat earlier before the -rc I'm supposed to be pushing them for. > > Yeah, that's what I try too. But this time the patch itself came in on > July 13th and I sent the pull request on July 15th. > > I mentioned -rc7 as that was the next rc in line, but it was actually > fine for this to be applied after rc7 too, before the 5.19 release > though. Should I send the pull request (and tag) without mentioning > the rc number in future ? It definitely helps to indicate that it is a "fixes" one that should be pushed for one of the upcoming -rcs, so I'm not sure. Perhaps, if you say "-rc7" it is better to mention that -rc8 or later will work too.
The following changes since commit be4b61ec45b3efe5e9077525fc92d544305eb2a6: cpufreq: Add MT8186 to cpufreq-dt-platdev blocklist (2022-06-28 13:34:56 +0530) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git tags/cpufreq-arm-fixes-5.19-rc7 for you to fetch changes up to d2394860b45c3c1484e4b0a5d09909a1e3f6569e: cpufreq: mediatek: Handle sram regulator probe deferral (2022-07-13 16:51:32 +0530) ---------------------------------------------------------------- cpufreq arm fixes for 5.19-rc6 - mediatek: Handle sram regulator probe deferral ---------------------------------------------------------------- AngeloGioacchino Del Regno (1): cpufreq: mediatek: Handle sram regulator probe deferral drivers/cpufreq/mediatek-cpufreq.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)