linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Balantzyan <mbalant3@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Mark Balantzyan <mbalant3@gmail.com>,
	linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org,
	wim@linux-watchdog.org
Subject: Re: [PATCH] watchdog device drivers:pc87413_wdt: Rewriting of pc87413_wdt driver to utilize common watchdog interface (fwd)
Date: Mon, 29 Jul 2019 17:44:39 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.1907291732130.20898@mbalantz-desktop> (raw)
In-Reply-To: <8e159e06-023e-6e20-ced5-3a645c0a1242@roeck-us.net>

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


  reply	other threads:[~2019-07-30  0:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 23:17 [PATCH] watchdog device drivers:pc87413_wdt: Rewriting of pc87413_wdt driver to utilize common watchdog interface (fwd) Mark Balantzyan
2019-07-30  0:26 ` Guenter Roeck
2019-07-30  0:44   ` Mark Balantzyan [this message]
2019-07-30  1:30     ` Guenter Roeck
2019-07-30  2:21       ` Mark Balantzyan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1907291732130.20898@mbalantz-desktop \
    --to=mbalant3@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=wim@linux-watchdog.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).