From: Stephen Boyd <sboyd@codeaurora.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2] clk-mux: Improve a size determination in clk_hw_register_mux_table()
Date: Tue, 14 Nov 2017 01:57:27 +0000 [thread overview]
Message-ID: <20171114015727.GD11955@codeaurora.org> (raw)
In-Reply-To: <7d70d3de-ba3b-3619-05a8-9a4abe0dacfe@users.sourceforge.net>
On 09/26, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Tue, 26 Sep 2017 17:30:06 +0200
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the corresponding size
> determination a bit safer according to the Linux coding style convention.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2] clk-mux: Improve a size determination in clk_hw_register_mux_table()
Date: Mon, 13 Nov 2017 17:57:27 -0800 [thread overview]
Message-ID: <20171114015727.GD11955@codeaurora.org> (raw)
In-Reply-To: <7d70d3de-ba3b-3619-05a8-9a4abe0dacfe@users.sourceforge.net>
On 09/26, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Tue, 26 Sep 2017 17:30:06 +0200
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the corresponding size
> determination a bit safer according to the Linux coding style convention.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-11-14 1:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 16:20 [PATCH 0/2] clk-mux: Adjustments for clk_hw_register_mux_table() SF Markus Elfring
2017-09-26 16:20 ` SF Markus Elfring
2017-09-26 16:21 ` [PATCH 1/2] clk-mux: Delete an error message for a failed memory allocation in clk_hw_register_mux_t SF Markus Elfring
2017-09-26 16:21 ` [PATCH 1/2] clk-mux: Delete an error message for a failed memory allocation in clk_hw_register_mux_table() SF Markus Elfring
2017-11-14 1:57 ` [PATCH 1/2] clk-mux: Delete an error message for a failed memory allocation in clk_hw_register_m Stephen Boyd
2017-11-14 1:57 ` [PATCH 1/2] clk-mux: Delete an error message for a failed memory allocation in clk_hw_register_mux_table() Stephen Boyd
2017-09-26 16:22 ` [PATCH 2/2] clk-mux: Improve a size determination " SF Markus Elfring
2017-09-26 16:22 ` SF Markus Elfring
2017-11-14 1:57 ` Stephen Boyd [this message]
2017-11-14 1:57 ` 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=20171114015727.GD11955@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.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 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.