From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Stephen Boyd <sboyd@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
Cc: Kees Cook <keescook@chromium.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2 1/2][next] clk: visconti: Fix undefined behavior bug in struct visconti_pll_provider
Date: Mon, 23 Oct 2023 20:48:00 -0600 [thread overview]
Message-ID: <21b1ebbe-2bef-4f56-a4d6-3ed898a1e953@embeddedor.com> (raw)
In-Reply-To: <9ebe2372491a76253e5597086d059b1d.sboyd@kernel.org>
>> Fixes: b4cbe606dc36 ("clk: visconti: Add support common clock driver and reset driver")
>> Cc: stable@vger.kernel.org
>> Reviewed-by: Kees Cook <keescook@chromium.org>
>> Acked-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
>> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
>> ---
>
> Applied to clk-next
Hi!
Here is another similar small series, in case you missed it:
https://lore.kernel.org/linux-hardening/cover.1697493574.git.gustavoars@kernel.org/
Thanks
--
Gustavo
next prev parent reply other threads:[~2023-10-24 2:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 22:04 [PATCH v2 0/2][next] clk: visconti: Fix undefined behavior bug and add bounds-checking coverage Gustavo A. R. Silva
2023-10-16 22:05 ` [PATCH v2 1/2][next] clk: visconti: Fix undefined behavior bug in struct visconti_pll_provider Gustavo A. R. Silva
2023-10-24 2:40 ` Stephen Boyd
2023-10-24 2:48 ` Gustavo A. R. Silva [this message]
2023-10-24 2:52 ` Stephen Boyd
2023-10-16 22:06 ` [PATCH v2 2/2][next] clk: visconti: Add bounds-checking coverage for " Gustavo A. R. Silva
2023-10-24 2:40 ` 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=21b1ebbe-2bef-4f56-a4d6-3ed898a1e953@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=sboyd@kernel.org \
/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