[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190506035345.GJ14916@sirena.org.uk>
Date: Mon, 6 May 2019 12:53:45 +0900
From: Mark Brown <broonie@...nel.org>
To: "S.j. Wang" <shengjiu.wang@....com>
Cc: Nicolin Chen <nicoleotsuka@...il.com>,
"timur@...nel.org" <timur@...nel.org>,
"Xiubo.Lee@...il.com" <Xiubo.Lee@...il.com>,
"festevam@...il.com" <festevam@...il.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V4] ASoC: fsl_esai: Add pm runtime function
On Sun, May 05, 2019 at 03:28:59AM +0000, S.j. Wang wrote:
> We find that maybe it is caused by the Transfer-Encoding format.
> We sent the patch by the --transfer-encoding=8bit, but in the receiver side
> it shows:
]
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: base64
> It may be caused by our company's mail server. We are checking...
Ah, that looks likely... not sure I have any great suggestions for how
to resolve it but at least it looks like progress on figuring out the
cause, I haven't been able to see anything wrong locally.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists