Message ID | 20241120091507.1404368-1-quic_mdalam@quicinc.com (mailing list archive) |
---|---|
Headers | show |
Series | Add QPIC SPI NAND driver | expand |
Hi Marc, On 20/11/2024 at 14:44:58 +0530, Md Sadre Alam <quic_mdalam@quicinc.com> wrote: > v14: > * Updated commit message > * Fix spelling mistake > * Remove "inline" from multiple APIs from qcom_nandc.c file > * Move '|' in qcom_param_page_type_exec() APIs at the end of line I guess it is now time to move on, I can apply patches 2-5 and share an immutable tag. However, due to the frequent inconsistencies observed during the lifetime of this patchset, we might be slightly more conservative than usual and split the patches over two kernel releases. I fear there might be annoying fixes on the mtd side needed because of some side effects. Without these, the spi tree might have broken qcom support for several weeks. What do you think? Cheers, Miquèl
On 12/2/2024 10:27 PM, Miquel Raynal wrote: > Hi Marc, > > On 20/11/2024 at 14:44:58 +0530, Md Sadre Alam <quic_mdalam@quicinc.com> wrote: > >> v14: >> * Updated commit message >> * Fix spelling mistake >> * Remove "inline" from multiple APIs from qcom_nandc.c file >> * Move '|' in qcom_param_page_type_exec() APIs at the end of line > > I guess it is now time to move on, I can apply patches 2-5 and share an > immutable tag. However, due to the frequent inconsistencies observed > during the lifetime of this patchset, we might be slightly more > conservative than usual and split the patches over two kernel > releases. I fear there might be annoying fixes on the mtd side needed > because of some side effects. Without these, the spi tree might have > broken qcom support for several weeks. What do you think? Sorry for the delayed response. I'm fine with merging patches 2 to 5. I tested them on today's linux-next, and the driver performed as expected. > > Cheers, > Miquèl