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]
Message-ID: <20240903150826.749b8560@xps-13>
Date: Tue, 3 Sep 2024 15:08:26 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Md Sadre Alam <quic_mdalam@...cinc.com>
Cc: <broonie@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
 <conor+dt@...nel.org>, <andersson@...nel.org>, <konradybcio@...nel.org>,
 <richard@....at>, <vigneshr@...com>, <manivannan.sadhasivam@...aro.org>,
 <esben@...nix.com>, <linux-arm-msm@...r.kernel.org>,
 <linux-spi@...r.kernel.org>, <devicetree@...r.kernel.org>,
 <linux-kernel@...r.kernel.org>, <linux-mtd@...ts.infradead.org>
Subject: Re: [PATCH v8 0/8] Add QPIC SPI NAND driver

Hi,

quic_mdalam@...cinc.com wrote on Tue, 3 Sep 2024 14:45:15 +0530:

> Hi Miquel,
> 
> On 8/20/2024 4:12 PM, Md Sadre Alam wrote:
> > v8:
> >   * Fixed compilation warning reported by kernel test robot
> >   * Added "chip" description in nandc_set_read_loc_first()
> >   * Added "chip" description" in nandc_set_read_loc_last()
> >   * Changed data type of read_location0, read_location1,
> >     read_location2, read_location3, addr0, addr1, cmd, cfg0,
> >     cfg1, ecc_bch_cfg, ecc_buf_cfg, clrflashstatus, clrreadstatus,
> >     orig_cmd1, orig_vld to __le32 to fix compilation warning.
> >   * Included bitfield.h header file in spi-qpic-snand.c to
> >     fix compilation warning
> >   * Removed unused variable "steps" variable from
> >     qcom_spi_ecc_init_ctx_pipelined()
> >   
>      I have addressed your comments to v6 and further posted till v8.
>      Could you please let me know if this is fine.
>      and how to get this merged ?

There are still kernel test robot reports, so this means there are
issues in your code that I don't need to point out explicitly, but I am
actively waiting for them to be fixed.

Thanks,
Miquèl

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ