From: Markus Elfring <Markus.Elfring@web.de>
To: Mark Brown <broonie@kernel.org>, Felix Gu <gu_0233@qq.com>,
linux-spi@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
Orson Zhai <orsonzhai@gmail.com>
Subject: Re: [PATCH v2] spi: spi-sprd-adi: Fix double free in probe error path
Date: Tue, 13 Jan 2026 20:20:29 +0100 [thread overview]
Message-ID: <1c068a91-e0a9-4edd-b5d0-c7fde56999f7@web.de> (raw)
In-Reply-To: <176830457213.25724.9815535994112539882.b4-ty@kernel.org>
> [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
next prev parent reply other threads:[~2026-01-13 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 12:49 [PATCH v2] spi: spi-sprd-adi: Fix double free in probe error path Felix Gu
2026-01-09 17:40 ` Markus Elfring
2026-01-13 11:42 ` Mark Brown
2026-01-13 19:20 ` Markus Elfring [this message]
2026-01-13 19:25 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c068a91-e0a9-4edd-b5d0-c7fde56999f7@web.de \
--to=markus.elfring@web.de \
--cc=baolin.wang@linux.alibaba.com \
--cc=broonie@kernel.org \
--cc=gu_0233@qq.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=zhang.lyra@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox