public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Gilles Buloz <Gilles.Buloz@kontron.com>
Cc: "linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>
Subject: Re: hwmon: (nct7802) buggy VSEN1/2/3 alarm
Date: Thu, 28 Nov 2019 07:22:40 -0800	[thread overview]
Message-ID: <d191c93b-b78d-a2ab-317e-e7eb7a923f8b@roeck-us.net> (raw)
In-Reply-To: <5DDFA5DE.5080102@kontron.com>

On 11/28/19 2:47 AM, Gilles Buloz wrote:
> Please find the inlined patches according to your feedback. I've also fixed some typos and added a mutex_lock/unlock in in_alarm_show().
> See also my replies to your questions in the previous mail below
> 

Please don't send final patches inline, nor as reply to previous e-mails.
Doing this violates Documentation/process/submitting-patches.rst.
Besides, I use patchwork for my workflow, patchwork gets confused by it,
and the patches don't show up there.

On top of that, the patches are whitespace damaged (tabs replaced with spaces)
and would not apply, even if I tried.

Guenter

      reply	other threads:[~2019-11-28 15:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 13:13 hwmon: (nct7802) buggy VSEN1/2/3 alarm Gilles Buloz
2019-11-25 14:31 ` Guenter Roeck
2019-11-25 16:44   ` Gilles Buloz
2019-11-25 17:35     ` Guenter Roeck
2019-11-25 18:06       ` Gilles Buloz
2019-11-26 10:03         ` Gilles Buloz
2019-11-26 12:22           ` Guenter Roeck
2019-11-26 16:47             ` Gilles Buloz
2019-11-26 18:20               ` Guenter Roeck
2019-11-27 10:42                 ` Gilles Buloz
2019-11-27 14:41                 ` Gilles Buloz
2019-11-27 19:32                   ` Guenter Roeck
2019-11-28 10:47                     ` Gilles Buloz
2019-11-28 15:22                       ` Guenter Roeck [this message]

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=d191c93b-b78d-a2ab-317e-e7eb7a923f8b@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=Gilles.Buloz@kontron.com \
    --cc=linux-hwmon@vger.kernel.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