From: Dan Carpenter <dan.carpenter@oracle.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] rtc: at91rm9200: double locking bug in at91_rtc_interrupt()
Date: Tue, 17 Mar 2015 17:32:35 +0000 [thread overview]
Message-ID: <20150317173235.GM10964@mwanda> (raw)
In-Reply-To: <1426606690-18947-1-git-send-email-nicolas.ferre@atmel.com>
On Tue, Mar 17, 2015 at 04:38:10PM +0100, Nicolas Ferre wrote:
> Reported-also-by: David Dueck <davidcdueck@googlemail.com>
The point of tags is that you collect them by doing:
`git log | grep Reported-by: | sort | uniq -c | sort -rn` to see if you
are the winner. It gives me an unfair advantage if you get creative
with David's tag.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, a.zummo@towertech.it,
rtc-linux@googlegroups.com, kernel-janitors@vger.kernel.org,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Subject: Re: [PATCH] rtc: at91rm9200: double locking bug in at91_rtc_interrupt()
Date: Tue, 17 Mar 2015 20:32:35 +0300 [thread overview]
Message-ID: <20150317173235.GM10964@mwanda> (raw)
In-Reply-To: <1426606690-18947-1-git-send-email-nicolas.ferre@atmel.com>
On Tue, Mar 17, 2015 at 04:38:10PM +0100, Nicolas Ferre wrote:
> Reported-also-by: David Dueck <davidcdueck@googlemail.com>
The point of tags is that you collect them by doing:
`git log | grep Reported-by: | sort | uniq -c | sort -rn` to see if you
are the winner. It gives me an unfair advantage if you get creative
with David's tag.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: dan.carpenter@oracle.com (Dan Carpenter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] rtc: at91rm9200: double locking bug in at91_rtc_interrupt()
Date: Tue, 17 Mar 2015 20:32:35 +0300 [thread overview]
Message-ID: <20150317173235.GM10964@mwanda> (raw)
In-Reply-To: <1426606690-18947-1-git-send-email-nicolas.ferre@atmel.com>
On Tue, Mar 17, 2015 at 04:38:10PM +0100, Nicolas Ferre wrote:
> Reported-also-by: David Dueck <davidcdueck@googlemail.com>
The point of tags is that you collect them by doing:
`git log | grep Reported-by: | sort | uniq -c | sort -rn` to see if you
are the winner. It gives me an unfair advantage if you get creative
with David's tag.
regards,
dan carpenter
next prev parent reply other threads:[~2015-03-17 17:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 10:48 [patch] rtc: at91rm9200: double locking bug in at91_rtc_interrupt() Dan Carpenter
2015-03-15 11:01 ` Boris Brezillon
2015-03-17 15:38 ` [PATCH] " Nicolas Ferre
2015-03-17 15:38 ` Nicolas Ferre
2015-03-17 15:38 ` Nicolas Ferre
2015-03-17 17:32 ` Dan Carpenter [this message]
2015-03-17 17:32 ` Dan Carpenter
2015-03-17 17:32 ` Dan Carpenter
2015-03-18 0:56 ` Rafael J. Wysocki
2015-03-18 1:20 ` Rafael J. Wysocki
2015-03-18 1:20 ` Rafael J. Wysocki
2015-03-17 15:39 ` [patch] " Nicolas Ferre
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=20150317173235.GM10964@mwanda \
--to=dan.carpenter@oracle.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 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.