lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 30 Aug 2018 09:19:28 +0000
From:   Chuanhua Han <chuanhua.han@....com>
To:     Boris Brezillon <boris.brezillon@...tlin.com>
CC:     "broonie@...nel.org" <broonie@...nel.org>,
        "linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: RE: [PATCH v5] spi: spi-mem: Adjust op len based on message/transfer
 size limitations



> -----Original Message-----
> From: Boris Brezillon <boris.brezillon@...tlin.com>
> Sent: 2018年8月30日 17:17
> To: Chuanhua Han <chuanhua.han@....com>
> Cc: broonie@...nel.org; linux-spi@...r.kernel.org;
> linux-kernel@...r.kernel.org; stable@...r.kernel.org
> Subject: Re: [PATCH v5] spi: spi-mem: Adjust op len based on message/transfer
> size limitations
> 
> On Thu, 30 Aug 2018 09:13:03 +0000
> Chuanhua Han <chuanhua.han@....com> wrote:
> 
> > > -----Original Message-----
> > > From: Boris Brezillon <boris.brezillon@...tlin.com>
> > > Sent: 2018年8月30日 16:47
> > > To: Chuanhua Han <chuanhua.han@....com>
> > > Cc: broonie@...nel.org; linux-spi@...r.kernel.org;
> > > linux-kernel@...r.kernel.org; stable@...r.kernel.org
> > > Subject: Re: [PATCH v5] spi: spi-mem: Adjust op len based on
> > > message/transfer size limitations
> > >
> > > Hi Chuanhua,
> > >
> > > On Thu, 30 Aug 2018 16:43:24 +0800
> > > Chuanhua Han <chuanhua.han@....com> wrote:
> > >
> > > > We need that to adjust the len of the 2nd transfer (called data in
> > > > spi-mem) if it's too long to fit in a SPI message or SPI transfer.
> > >
> > > You already sent this email a few days back. Please wait a bit
> > > before sending it again. And when you do so and nothing changed in
> > > the patch please use the [PATCH RESEND vX] prefix and explain why you
> resend it.
> > I have modified the patch for the comment you mentioned last time. Do
> > you need any other modification?
> 
> Oops, sorry. Looks like the previous one was only sent to me, not the ML and
> the SPI maintainer.
It doesn't matter,thank you for your valuable advice!

Powered by blists - more mailing lists