From: Stephen Boyd <sboyd@kernel.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>,
amergnat@baylibre.com, angelogioacchino.delregno@collabora.com,
cw00.choi@samsung.com, frank.li@vivo.com,
kevin-cw.chen@mediatek.com, luca.ceresoli@bootlin.com,
macpaul.lin@mediatek.com, mars.cheng@mediatek.com,
matthias.bgg@gmail.com, msp@baylibre.com,
mturquette@baylibre.com, owen.chen@mediatek.com, robh@kernel.org,
ryder.lee@mediatek.com, u.kleine-koenig@pengutronix.de,
wendell.lin@mediatek.com, wenst@chromium.org,
wenzhen.yu@mediatek.com
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Jiasheng Jiang <jiasheng@iscas.ac.cn>
Subject: Re: [PATCH 4/5] clk: mediatek: clk-mt7629-eth: Add check for mtk_alloc_clk_data
Date: Wed, 18 Oct 2023 18:15:56 -0700 [thread overview]
Message-ID: <73db73cf73cb14cf9d526a9fec7d1344.sboyd@kernel.org> (raw)
In-Reply-To: <20230912093407.21505-4-jiasheng@iscas.ac.cn>
Quoting Jiasheng Jiang (2023-09-12 02:34:06)
> Add the check for the return value of mtk_alloc_clk_data() in order to
> avoid NULL pointer dereference.
>
> Fixes: 3b5e748615e7 ("clk: mediatek: add clock support for MT7629 SoC")
> Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
> ---
Applied to clk-next
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-19 1:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 9:34 [PATCH 1/5] clk: mediatek: clk-mt6765: Add check for mtk_alloc_clk_data Jiasheng Jiang
2023-09-12 9:34 ` [PATCH 2/5] clk: mediatek: clk-mt6779: " Jiasheng Jiang
2023-09-12 10:02 ` AngeloGioacchino Del Regno
2023-10-19 1:15 ` Stephen Boyd
2023-09-12 9:34 ` [PATCH 3/5] clk: mediatek: clk-mt6797: " Jiasheng Jiang
2023-09-12 10:02 ` AngeloGioacchino Del Regno
2023-10-19 1:15 ` Stephen Boyd
2023-09-12 9:34 ` [PATCH 4/5] clk: mediatek: clk-mt7629-eth: " Jiasheng Jiang
2023-09-12 10:02 ` AngeloGioacchino Del Regno
2023-10-19 1:15 ` Stephen Boyd [this message]
2023-09-12 9:34 ` [PATCH 5/5] clk: mediatek: clk-mt7629: " Jiasheng Jiang
2023-09-12 10:02 ` AngeloGioacchino Del Regno
2023-10-19 1:16 ` Stephen Boyd
2023-09-12 10:02 ` [PATCH 1/5] clk: mediatek: clk-mt6765: " AngeloGioacchino Del Regno
2023-10-19 1:15 ` Stephen Boyd
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=73db73cf73cb14cf9d526a9fec7d1344.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=cw00.choi@samsung.com \
--cc=frank.li@vivo.com \
--cc=jiasheng@iscas.ac.cn \
--cc=kevin-cw.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luca.ceresoli@bootlin.com \
--cc=macpaul.lin@mediatek.com \
--cc=mars.cheng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=msp@baylibre.com \
--cc=mturquette@baylibre.com \
--cc=owen.chen@mediatek.com \
--cc=robh@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wendell.lin@mediatek.com \
--cc=wenst@chromium.org \
--cc=wenzhen.yu@mediatek.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;
as well as URLs for NNTP newsgroup(s).