From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: nand: orion: fix clk handling
Date: Thu, 16 Mar 2017 10:05:39 +0100 [thread overview]
Message-ID: <20170316100539.15bb1828@bbrezillon> (raw)
In-Reply-To: <20170312213406.20987-1-gmbnomis@gmail.com>
Hi Simon,
On Sun, 12 Mar 2017 22:34:06 +0100
Simon Baatz <gmbnomis@gmail.com> wrote:
> The clk handling in orion_nand.c had two problems:
>
> - In the probe function, clk_put() was called for an enabled clock,
> which violates the API (see documentation for clk_put() in
> include/linux/clk.h)
>
> - In the error path of the probe function, clk_put() could be called
> twice for the same clock.
>
> In order to clean this up, use the managed function devm_clk_get() and
> store the pointer to the clk in the driver data.
>
> Fixes: baffab28b13120694fa3ebab08d3e99667a851d2 ('ARM: Orion: fix driver probe error handling with respect to clk')
> Cc: <stable@vger.kernel.org> # v4.5+
> Signed-off-by: Simon Baatz <gmbnomis@gmail.com>
> ---
> drivers/mtd/nand/orion_nand.c | 42 +++++++++++++++++++++---------------------
> 1 file changed, 21 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/mtd/nand/orion_nand.c b/drivers/mtd/nand/orion_nand.c
> index 4a91c5d000be..b355aa738fae 100644
> --- a/drivers/mtd/nand/orion_nand.c
> +++ b/drivers/mtd/nand/orion_nand.c
> @@ -23,6 +23,11 @@
> #include <asm/sizes.h>
> #include <linux/platform_data/mtd-orion_nand.h>
>
> +struct orion_nand_info {
> + struct nand_chip chip;
> + struct clk *clk;
Can we avoid this kind of alignment, which will not be preserved if
someone adds a new field with a type that is longer than "struct
nand_chip "?
Regards,
Boris
next prev parent reply other threads:[~2017-03-16 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 21:34 [PATCH] mtd: nand: orion: fix clk handling Simon Baatz
2017-03-13 7:12 ` Uwe Kleine-König
2017-03-13 20:43 ` Simon Baatz
2017-03-13 20:58 ` Uwe Kleine-König
2017-03-16 9:12 ` Boris Brezillon
2017-03-16 21:50 ` Simon Baatz
2017-03-17 6:36 ` Boris Brezillon
2017-03-16 9:05 ` Boris Brezillon [this message]
2017-03-16 21:44 ` Simon Baatz
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=20170316100539.15bb1828@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@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 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).