From: Jerome Brunet <jbrunet@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Kevin Hilman <khilman@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Carlo Caione <carlo@caione.org>,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] clk: meson: fix protection against undefined clks
Date: Thu, 27 Jul 2017 18:17:53 +0200 [thread overview]
Message-ID: <20170727161755.10393-1-jbrunet@baylibre.com> (raw)
If the last clkids defined have no hw pointer associated with them in
the hw_onecell_data array, the initialization is going to crash badly
because the array is not big enough.
The patchset makes sure the array is big enough, and that each clkid is
associated with a valid hw pointer, or NULL.
Doing it in two patches to ease backport, since we are not fixing the
same commit on meson8b and gxbb
Jerome Brunet (2):
clk: meson: meson8b: fix protection against undefined clks
clk: meson: gxbb: fix protection against undefined clks
drivers/clk/meson/gxbb.c | 2 ++
drivers/clk/meson/meson8b.c | 1 +
2 files changed, 3 insertions(+)
--
2.9.4
next reply other threads:[~2017-07-27 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 16:17 Jerome Brunet [this message]
2017-07-27 16:17 ` [PATCH 1/2] clk: meson: meson8b: fix protection against undefined clks Jerome Brunet
2017-07-27 16:17 ` [PATCH 2/2] clk: meson: gxbb: " Jerome Brunet
2017-07-28 10:07 ` [PATCH 0/2] clk: meson: " Neil Armstrong
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=20170727161755.10393-1-jbrunet@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=carlo@caione.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).