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]
Message-ID: <alpine.DEB.2.21.1907291732130.20898@mbalantz-desktop>
Date:   Mon, 29 Jul 2019 17:44:39 -0700 (PDT)
From:   Mark Balantzyan <mbalant3@...il.com>
To:     Guenter Roeck <linux@...ck-us.net>
cc:     Mark Balantzyan <mbalant3@...il.com>, linux-kernel@...r.kernel.org,
        linux-watchdog@...r.kernel.org, wim@...ux-watchdog.org
Subject: Re: [PATCH] watchdog device drivers:pc87413_wdt: Rewriting of
 pc87413_wdt driver to utilize common watchdog interface (fwd)

Hello all, Guenter,

I am being evaluated as a student by my organization. I appreciate your 
patience with my emails and patches.

I would like to please propose that we divide and conquer: I write the 
code for converting the driver to common watchdog interface (and I thank 
you for your guidance on it in previous email) and you test the code on 
the actual hardware you may happen to have, as I do not have it. I accept 
the fact that it is indeed risky without the hardware to ensure the driver 
works correctly, but that will be where we work in tandem, software to 
hardware, yes, if that's alright?

I think it's better if I use git send-email for the corresponding patch 
with the improvements you forecasted since it may format things better and 
may result in a non-corrupted patching.

Thank you,
Mark

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ