All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [V2 2/4] rtc: fix 88pm860x rtc irq enable callback
Date: Wed, 28 Mar 2012 11:06:17 +0100	[thread overview]
Message-ID: <20120328100617.GB3232@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120327164759.ec04c62e.akpm@linux-foundation.org>

On Tue, Mar 27, 2012 at 04:47:59PM -0700, Andrew Morton wrote:

> It's surprising that the driver has been in-tree for a year and nobody
> has noticed this bug.  This makes me wonder if the fix is wrong.

I rather suspect few of the boards that use this chip ever run mainline
and we're seeing the effects of Android's ICS release rolling out here -
it's using 3.0 as the default kernel which was the first version which
included this driver as standard.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120328/9915d3a0/attachment.sig>

      reply	other threads:[~2012-03-28 10:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 11:47 [V1 1/4] regulator: fix the ldo configure according to 88pm860x spec Jett.Zhou
     [not found] ` <1329997662-2931-3-git-send-email-jtzhou@marvell.com>
2012-02-24  8:41   ` [V1 3/4] mfd: Add ability to wake the system for 88pm860x Dmitry Torokhov
     [not found]   ` <1330073981-25793-1-git-send-email-jtzhou@marvell.com>
2012-02-27 14:45     ` [V2 " Samuel Ortiz
     [not found] ` <1331259874-26503-1-git-send-email-jtzhou@marvell.com>
2012-03-27 23:47   ` [V2 2/4] rtc: fix 88pm860x rtc irq enable callback Andrew Morton
2012-03-28 10:06     ` Mark Brown [this message]

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=20120328100617.GB3232@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.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.