From: patchwork-bot+linux-amlogic@kernel.org
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH] clk: meson: g12a: fix missing uart2 in regmap table
Date: Mon, 16 Dec 2019 20:01:14 +0000 [thread overview]
Message-ID: <157652647477.23523.12091333592301895101.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20191213103304.12867-1-jbrunet@baylibre.com>
Hello:
This patch was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Fri, 13 Dec 2019 11:33:04 +0100 you wrote:
> UART2 peripheral is missing from the regmap fixup table of the g12a family
> clock controller. As it is, any access to this clock would Oops, which is
> not great.
>
> Add the clock to the table to fix the problem.
>
> Fixes: 085a4ea93d54 ("clk: meson: g12a: add peripheral clock controller")
> Reported-by: Dmitry Shmidt <dimitrysh@google.com>
> Tested-by: Dmitry Shmidt <dimitrysh@google.com>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
>
> [...]
Here is a summary with links:
- clk: meson: g12a: fix missing uart2 in regmap table
https://git.kernel.org/khilman/linux-amlogic/c/b1b3f0622a9d52ac19a63619911823c89a4d85a4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-12-16 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 10:33 [PATCH] clk: meson: g12a: fix missing uart2 in regmap table Jerome Brunet
2019-12-13 10:33 ` Jerome Brunet
2019-12-13 10:34 ` Neil Armstrong
2019-12-13 10:34 ` Neil Armstrong
2019-12-13 16:44 ` Kevin Hilman
2019-12-13 16:44 ` Kevin Hilman
2019-12-16 9:30 ` Jerome Brunet
2019-12-16 9:30 ` Jerome Brunet
2019-12-16 20:01 ` patchwork-bot+linux-amlogic [this message]
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=157652647477.23523.12091333592301895101.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.