linux-kernel - Re: [GIT PULL] mtd: topic branch for spi with Qcom changes

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] [day] [month] [year] [list]

Message-ID: <5022bc8c-a6ac-3782-43cc-19b0ca644a6a@quicinc.com>
Date: Thu, 20 Feb 2025 17:03:34 +0530
From: Md Sadre Alam <quic_mdalam@...cinc.com>
To: Mark Brown <broonie@...nel.org>
CC: Miquel Raynal <miquel.raynal@...tlin.com>, <andersson@...nel.org>,
        <konradybcio@...nel.org>, <richard@....at>, <vigneshr@...com>,
        <manivannan.sadhasivam@...aro.org>, <linux-arm-msm@...r.kernel.org>,
        <linux-spi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-mtd@...ts.infradead.org>,
        Tudor Ambarus <Tudor.Ambarus@...aro.org>,
        Frieder Schrempf <frieder.schrempf@...tron.de>,
        Michael Walle
	<michael@...le.cc>,
        Pratyush Yadav <pratyush@...nel.org>, <quic_srichara@...cinc.com>,
        <quic_varada@...cinc.com>
Subject: Re: [GIT PULL] mtd: topic branch for spi with Qcom changes



On 2/18/2025 8:24 PM, Mark Brown wrote:
> On Mon, Feb 17, 2025 at 11:25:24AM +0530, Md Sadre Alam wrote:
>> On 1/6/2025 9:06 PM, Mark Brown wrote:
> 
>>> Thanks for the heads up - I didn't pull it yet so as you suggest I can
>>> just leave it and pick things up from mainline.
> 
>> The QPIC raw nand patches are available in the linux-next. could you please
>> pick the QPIC SPI NAND patches [1]
>> [1]
>> https://lore.kernel.org/all/20241120091507.1404368-7-quic_mdalam@quicinc.com/
> 
> That looks like it was posted back in November, I'd have expected
> anything for this release to have been posted after the merge window...
> 
> Please don't send content free pings and please allow a reasonable time
> for review.  People get busy, go on holiday, attend conferences and so
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review.  If there have been
> review comments then people may be waiting for those to be addressed.
> 
> Sending content free pings adds to the mail volume (if they are seen at
> all) which is often the problem and since they can't be reviewed
> directly if something has gone wrong you'll have to resend the patches
> anyway, so sending again is generally a better approach though there are
> some other maintainers who like them - if in doubt look at how patches
> for the subsystem are normally handled.
Sorry, will rebase, test and post a new version.

Thanks,
Alam.