| Message ID | 20190809115930.6050-1-paul@crapouillou.net (mailing list archive) |
|---|---|
| Headers | show |
| Series | watchdog: jz4740: Driver update | expand |
On Fri, Aug 09, 2019 at 01:59:27PM +0200, Paul Cercueil wrote: > Hi, > > This patchset comes from a bigger patchset that was cut in smaller > pieces for easier integration to mainline. > (The patchset was https://lkml.org/lkml/2019/3/27/1837) > > The reviews were kept since the code mostly didn't change. The exception > is the use of device_node_to_regmap() in patch 2/3. This function was > added in a prior patch, now merged in the MIPS tree. > > For that reason this patchset is based on the ingenic-tcu-v5.4 branch of > the MIPS tree > (git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git). > What is the expectation here ? Should the series be sent upstream through the watchdog tree, or through some other tree ? Thanks, Guenter
Hi Guenter, Le ven. 9 août 2019 à 18:52, Guenter Roeck <linux@roeck-us.net> a écrit : > On Fri, Aug 09, 2019 at 01:59:27PM +0200, Paul Cercueil wrote: >> Hi, >> >> This patchset comes from a bigger patchset that was cut in smaller >> pieces for easier integration to mainline. >> (The patchset was https://lkml.org/lkml/2019/3/27/1837) >> >> The reviews were kept since the code mostly didn't change. The >> exception >> is the use of device_node_to_regmap() in patch 2/3. This function >> was >> added in a prior patch, now merged in the MIPS tree. >> >> For that reason this patchset is based on the ingenic-tcu-v5.4 >> branch of >> the MIPS tree >> (git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git). >> > > What is the expectation here ? Should the series be sent upstream > through the watchdog tree, or through some other tree ? You can get it through the watchdog tree if you merge the ingenic-tcu-v5.4 branch from the MIPS tree. If you'd rather not do that, I can get it merged through the MIPS tree. Thanks, -Paul
On Fri, Aug 09, 2019 at 06:55:26PM +0200, Paul Cercueil wrote: > Hi Guenter, > > > Le ven. 9 août 2019 à 18:52, Guenter Roeck <linux@roeck-us.net> a écrit : > >On Fri, Aug 09, 2019 at 01:59:27PM +0200, Paul Cercueil wrote: > >> Hi, > >> > >> This patchset comes from a bigger patchset that was cut in smaller > >> pieces for easier integration to mainline. > >> (The patchset was https://lkml.org/lkml/2019/3/27/1837) > >> > >> The reviews were kept since the code mostly didn't change. The > >>exception > >> is the use of device_node_to_regmap() in patch 2/3. This function was > >> added in a prior patch, now merged in the MIPS tree. > >> > >> For that reason this patchset is based on the ingenic-tcu-v5.4 branch > >>of > >> the MIPS tree > >> (git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git). > >> > > > >What is the expectation here ? Should the series be sent upstream > >through the watchdog tree, or through some other tree ? > > You can get it through the watchdog tree if you merge the ingenic-tcu-v5.4 > branch from the MIPS tree. If you'd rather not do that, I can get it merged > through the MIPS tree. > I would prefer a merge through the mips tree. Guenter
Le ven. 9 août 2019 à 19:29, Guenter Roeck <linux@roeck-us.net> a écrit : > On Fri, Aug 09, 2019 at 06:55:26PM +0200, Paul Cercueil wrote: >> Hi Guenter, >> >> >> Le ven. 9 août 2019 à 18:52, Guenter Roeck <linux@roeck-us.net> a >> écrit : >> >On Fri, Aug 09, 2019 at 01:59:27PM +0200, Paul Cercueil wrote: >> >> Hi, >> >> >> >> This patchset comes from a bigger patchset that was cut in >> smaller >> >> pieces for easier integration to mainline. >> >> (The patchset was https://lkml.org/lkml/2019/3/27/1837) >> >> >> >> The reviews were kept since the code mostly didn't change. The >> >>exception >> >> is the use of device_node_to_regmap() in patch 2/3. This >> function was >> >> added in a prior patch, now merged in the MIPS tree. >> >> >> >> For that reason this patchset is based on the ingenic-tcu-v5.4 >> branch >> >>of >> >> the MIPS tree >> >> (git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git). >> >> >> > >> >What is the expectation here ? Should the series be sent upstream >> >through the watchdog tree, or through some other tree ? >> >> You can get it through the watchdog tree if you merge the >> ingenic-tcu-v5.4 >> branch from the MIPS tree. If you'd rather not do that, I can get >> it merged >> through the MIPS tree. >> > I would prefer a merge through the mips tree. > > Guenter Ok; Can I get some signatures then? ;) Thanks, -Paul
On Fri, Aug 09, 2019 at 07:34:49PM +0200, Paul Cercueil wrote: > > > Le ven. 9 août 2019 à 19:29, Guenter Roeck <linux@roeck-us.net> a écrit : > >On Fri, Aug 09, 2019 at 06:55:26PM +0200, Paul Cercueil wrote: > >> Hi Guenter, > >> > >> > >> Le ven. 9 août 2019 à 18:52, Guenter Roeck <linux@roeck-us.net> a écrit > >>: > >> >On Fri, Aug 09, 2019 at 01:59:27PM +0200, Paul Cercueil wrote: > >> >> Hi, > >> >> > >> >> This patchset comes from a bigger patchset that was cut in smaller > >> >> pieces for easier integration to mainline. > >> >> (The patchset was https://lkml.org/lkml/2019/3/27/1837) > >> >> > >> >> The reviews were kept since the code mostly didn't change. The > >> >>exception > >> >> is the use of device_node_to_regmap() in patch 2/3. This function > >>was > >> >> added in a prior patch, now merged in the MIPS tree. > >> >> > >> >> For that reason this patchset is based on the ingenic-tcu-v5.4 > >>branch > >> >>of > >> >> the MIPS tree > >> >> (git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git). > >> >> > >> > > >> >What is the expectation here ? Should the series be sent upstream > >> >through the watchdog tree, or through some other tree ? > >> > >> You can get it through the watchdog tree if you merge the > >>ingenic-tcu-v5.4 > >> branch from the MIPS tree. If you'd rather not do that, I can get it > >>merged > >> through the MIPS tree. > >> > >I would prefer a merge through the mips tree. > > > >Guenter > > Ok; Can I get some signatures then? ;) > They are already tagged with my Reviewed-by:. Do you want an Acked-by: as well ? Sure, no problem. Guenter