From: Julia Lawall <julia.lawall@lip6.fr>
To: "Mylène Josserand" <mylene.josserand@free-electrons.com>
Cc: kbuild-all@01.org, alexandre.belloni@free-electrons.com,
rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] rtc: m41t80: add alarm functionality (fwd)
Date: Tue, 29 Mar 2016 11:20:49 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1603291119590.2534@hadrien> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2561 bytes --]
It looks suspicious. Please check.
thanks,
julia
---------- Forwarded message ----------
Date: Tue, 29 Mar 2016 15:36:02 +0800
From: kbuild test robot <fengguang.wu@intel.com>
To: kbuild@01.org
Cc: Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [PATCH 6/8] rtc: m41t80: add alarm functionality
CC: kbuild-all@01.org
In-Reply-To: <1932c2b8c5f0c5d89c0578c300c9e18a283e8df0.1459233897.git.mylene.josserand@free-electrons.com>
TO: "Mylène Josserand" <mylene.josserand@free-electrons.com>
CC: alexandre.belloni@free-electrons.com, rtc-linux@googlegroups.com
CC: Alessandro Zummo <a.zummo@towertech.it>, linux-kernel@vger.kernel.org, mylene.josserand@free-electrons.com
Hi Mylène,
[auto build test WARNING on abelloni/rtc-next]
[also build test WARNING on v4.6-rc1 next-20160329]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Myl-ne-Josserand/rtc-m41t80-update-sysfs-entries-export/20160329-150848
base: https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next
:::::: branch date: 27 minutes ago
:::::: commit date: 27 minutes ago
>> drivers/rtc/rtc-m41t80.c:105:2-8: preceding lock on line 101
git remote add linux-review https://github.com/0day-ci/linux
git remote update linux-review
git checkout 41be232d1b3079b5d675eea5e95fd7ab39c2a1b2
vim +105 drivers/rtc/rtc-m41t80.c
41be232d Mylène Josserand 2016-03-29 95 struct i2c_client *client = dev_id;
41be232d Mylène Josserand 2016-03-29 96 struct m41t80_data *m41t80 = i2c_get_clientdata(client);
41be232d Mylène Josserand 2016-03-29 97 struct mutex *lock = &m41t80->rtc->ops_lock;
41be232d Mylène Josserand 2016-03-29 98 unsigned long events = 0;
41be232d Mylène Josserand 2016-03-29 99 int flags, flags_afe;
41be232d Mylène Josserand 2016-03-29 100
41be232d Mylène Josserand 2016-03-29 @101 mutex_lock(lock);
41be232d Mylène Josserand 2016-03-29 102
41be232d Mylène Josserand 2016-03-29 103 flags_afe = i2c_smbus_read_byte_data(client, M41T80_REG_ALARM_MON);
41be232d Mylène Josserand 2016-03-29 104 if (flags_afe < 0)
41be232d Mylène Josserand 2016-03-29 @105 return IRQ_NONE;
41be232d Mylène Josserand 2016-03-29 106
41be232d Mylène Josserand 2016-03-29 107 flags = i2c_smbus_read_byte_data(client, M41T80_REG_FLAGS);
41be232d Mylène Josserand 2016-03-29 108 if (flags <= 0)
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2016-03-29 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 9:20 Julia Lawall [this message]
2016-03-29 10:08 ` Alexandre Belloni
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=alpine.DEB.2.10.1603291119590.2534@hadrien \
--to=julia.lawall@lip6.fr \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mylene.josserand@free-electrons.com \
--cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®