linux-kernel - Re: [PATCH 0/3] watchdog: jz4740: Driver update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 09 Aug 2019 18:55:26 +0200
From:   Paul Cercueil <paul@...pouillou.net>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Wim Van Sebroeck <wim@...ux-watchdog.org>, od@...c.me,
        linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] watchdog: jz4740: Driver update

Hi Guenter,


Le ven. 9 août 2019 à 18:52, Guenter Roeck <linux@...ck-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