[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1c068a91-e0a9-4edd-b5d0-c7fde56999f7@web.de>
Date: Tue, 13 Jan 2026 20:20:29 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Mark Brown <broonie@...nel.org>, Felix Gu <gu_0233@...com>,
linux-spi@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org,
Baolin Wang <baolin.wang@...ux.alibaba.com>,
Chunyan Zhang <zhang.lyra@...il.com>, Orson Zhai <orsonzhai@...il.com>
Subject: Re: [PATCH v2] spi: spi-sprd-adi: Fix double free in probe error path
> [1/1] spi: spi-sprd-adi: Fix double free in probe error path
> commit: 383d4f5cffcc8df930d95b06518a9d25a6d74aac
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git/commit/?id=383d4f5cffcc8df930d95b06518a9d25a6d74aac
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
See also once more:
Check “BAD_FIXES_TAG”
https://elixir.bootlin.com/linux/v6.19-rc4/source/scripts/checkpatch.pl#L3231-L3269
Regards,
Markus
Powered by blists - more mailing lists