From: Alexander Holler <holler@ahsoftware.de>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Axel Lin <axel.lin@ingics.com>,
Jonathan Cameron <jic23@kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: hid-sensor-time: Add missing spin_lock_init
Date: Thu, 17 Jan 2013 13:58:55 +0100 [thread overview]
Message-ID: <50F7F58F.30505@ahsoftware.de> (raw)
In-Reply-To: <CACnwZYfV=czMR=FLwQseubK-G8GnuiVW_wsnFKTnw=rHrZ8dgg@mail.gmail.com>
Am 17.01.2013 02:58, schrieb Thiago Farina:
> On Wed, Jan 16, 2013 at 11:49 PM, Axel Lin <axel.lin@ingics.com> wrote:
>> Signed-off-by: Axel Lin <axel.lin@ingics.com>
>> ---
>> drivers/rtc/rtc-hid-sensor-time.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/rtc/rtc-hid-sensor-time.c b/drivers/rtc/rtc-hid-sensor-time.c
>> index 0438c9e..31c5728 100644
>> --- a/drivers/rtc/rtc-hid-sensor-time.c
>> +++ b/drivers/rtc/rtc-hid-sensor-time.c
>> @@ -225,6 +225,7 @@ static int hid_time_probe(struct platform_device *pdev)
>>
>> platform_set_drvdata(pdev, time_state);
>>
>> + spin_lock_init(&time_state->lock_last_time);
> Can you explain in the commit message why it is missing?
>
> For people not familiar with this code that isn't obvious.
>
Every spinlock must be initialized once (to SPIN_LOCK_UNLOCKED or by
using spin_lock_init()). On most architectures SPIN_LOCK_UNLOCKED is
just zero, therefor the kzalloc of the time_state does it (which likely
is the case why I haven't spotted any error without the initialization),
but that doesn't isn't true for all architectures.
Regards,
Alexander
next prev parent reply other threads:[~2013-01-17 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 1:49 [PATCH] rtc: hid-sensor-time: Add missing spin_lock_init Axel Lin
2013-01-17 1:58 ` Thiago Farina
2013-01-17 12:58 ` Alexander Holler [this message]
2013-01-17 12:47 ` Alexander Holler
2013-01-20 12:02 ` Jonathan Cameron
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=50F7F58F.30505@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=a.zummo@towertech.it \
--cc=axel.lin@ingics.com \
--cc=jic23@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=tfransosi@gmail.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.