linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3.10-stable] at91sam9x5 rtc causes damage
Date: Thu, 8 Aug 2013 04:34:04 +0900	[thread overview]
Message-ID: <20130807193404.GA3248@kroah.com> (raw)
In-Reply-To: <52029EF7.3040105@interlog.com>

On Wed, Aug 07, 2013 at 03:24:39PM -0400, Douglas Gilbert wrote:
> On 13-08-07 03:08 PM, Greg KH wrote:
> >On Wed, Aug 07, 2013 at 12:49:55PM -0400, Douglas Gilbert wrote:
> >>This one probably needs more sign-offs but some folks seem to be
> >>away. It is pretty simple and fixed in the current lk 3.11.0-rc
> >>series. So it just impacts the lk 3.10 series including lk 3.10.5 .
> >>
> >>ChangeLog:
> >>   - without this patch members of the at91sam9x5 family (e.g.
> >>     at91sam9g25) that use the RTC will receive an unhandled
> >>     interrupt whenever they try to write to the RTC. In the
> >>     case of 9x5 SoCs that is the SYS interrupt shared with
> >>     several other things such as the debug port. Thereafter
> >>     the debug port becomes useless (for input), the RTC doesn't
> >>     work ...
> >>
> >>Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>
> >
> ><formletter>
> >
> >This is not the correct way to submit patches for inclusion in the
> >stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
> >for how to do this properly.
> >
> ></formletter>
> 
> Fine. I'll leave it.

Leave what?  Did you read the above file that shows how to get a patch
into the stable tree?  Follow that and all should be fine.

thanks,

greg k-h

      reply	other threads:[~2013-08-07 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 16:49 [PATCH 3.10-stable] at91sam9x5 rtc causes damage Douglas Gilbert
2013-08-07 19:08 ` Greg KH
2013-08-07 19:24   ` Douglas Gilbert
2013-08-07 19:34     ` Greg KH [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=20130807193404.GA3248@kroah.com \
    --to=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).