linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: razvan becheriu <razvan.becheriu@gmail.com>
Cc: Razvan Becheriu <razvan.becheriu@qualitance.com>,
	linux-watchdog@vger.kernel.org,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>, Ferry Toth <fntoth@gmail.com>
Subject: Re: [PATCH v1] watchdog: intel-mid_wdt: Add WATCHDOG_NOWAYOUT support
Date: Tue, 1 Oct 2019 23:32:51 +0300	[thread overview]
Message-ID: <20191001203251.GT32742@smile.fi.intel.com> (raw)
In-Reply-To: <CAJAoKi8aRHyySUM1mcuub_tgmE7fdLgRyajYF=fUf6QH0PvZPA@mail.gmail.com>

On Tue, Oct 01, 2019 at 10:08:53PM +0300, razvan becheriu wrote:
> PS: sry for sending this several times, I get a message like:
> Message may contain a virus
> Your message wasn't delivered to linux-watchdog@vger.kernel.org because it
> may contain a virus. Learn how to check for and prevent viruses.

You need to send the message as plain text. You may test yourself without
spamming people by sending to some other address which you have access to.

All there messages I got have HTML part. Usually it shows MUA misconfiguration.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2019-10-01 20:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 14:31 [PATCH v1] watchdog: intel-mid_wdt: Add WATCHDOG_NOWAYOUT support Andy Shevchenko
2019-09-30 13:15 ` Guenter Roeck
2019-10-29 17:42   ` Ferry Toth
2019-10-30  0:13     ` Guenter Roeck
     [not found] ` <CAJAoKi8aRHyySUM1mcuub_tgmE7fdLgRyajYF=fUf6QH0PvZPA@mail.gmail.com>
2019-10-01 20:32   ` Andy Shevchenko [this message]
     [not found] ` <CAJAoKi_c2XRi_tdJcc3MMS1=9d4WH_Tq9EmH30-GyXcPoJhXGA@mail.gmail.com>
2019-10-02  6:11   ` razvan becheriu
2019-10-02  8:31     ` Andy Shevchenko

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=20191001203251.GT32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=fntoth@gmail.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=razvan.becheriu@gmail.com \
    --cc=razvan.becheriu@qualitance.com \
    --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).