linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Yang, Shunyong" <shunyong.yang@hxt-semitech.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	"andy.gross@linaro.org" <andy.gross@linaro.org>,
	"david.brown@linaro.org" <david.brown@linaro.org>,
	Sinan Kaya <okaya@kernel.org>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Zheng, Joey" <yu.zheng@hxt-semitech.com>
Subject: Re: About some mail lost and random unsubscribe issues on this dmaengine list
Date: Wed, 9 Jan 2019 11:55:05 -0500	[thread overview]
Message-ID: <20190109165505.GC26670@mit.edu> (raw)
In-Reply-To: <e3a2d37d7bce44eb8d3a726a8f69c8d7@HXTBJIDCEMVIW02.hxtcorp.net>

On Wed, Jan 09, 2019 at 07:51:11AM +0000, Yang, Shunyong wrote:
> Hi, Vinod,
>   Thanks for your information. I will check with our IT.
> Shunyong.

The usual answer is generally over-enthuastic application of anti-SPAM
techniques, especially DMARC, which is fundamentally mailing-list hostile.

Cheers,

					- Ted

  reply	other threads:[~2019-01-09 16:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07  4:28 [PATCH 1/2] dmaengine: qcom_hidma: initialize tx flags in hidma_prep_dma_* Shunyong Yang
2018-12-07  4:29 ` [PATCH 2/2] dmaengine: qcom_hidma: assign channel cookie correctly Shunyong Yang
2018-12-08 20:28   ` Sinan Kaya
2018-12-14  1:03     ` Yang, Shunyong
2019-01-04  8:56       ` Yang, Shunyong
2019-01-09  1:35         ` About some mail lost and random unsubscribe issues on this dmaengine list Yang, Shunyong
2019-01-09  6:58           ` Vinod Koul
2019-01-09  7:51             ` Yang, Shunyong
2019-01-09 16:55               ` Theodore Y. Ts'o [this message]
2019-01-04 17:31   ` [PATCH 2/2] dmaengine: qcom_hidma: assign channel cookie correctly Vinod Koul

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=20190109165505.GC26670@mit.edu \
    --to=tytso@mit.edu \
    --cc=andy.gross@linaro.org \
    --cc=dan.j.williams@intel.com \
    --cc=david.brown@linaro.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okaya@kernel.org \
    --cc=shunyong.yang@hxt-semitech.com \
    --cc=vkoul@kernel.org \
    --cc=yu.zheng@hxt-semitech.com \
    /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).