public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation•org (Greg KH)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] USB: ohci-at91: fix null pointer in ohci_hcd_at91_overcurrent_irq
Date: Tue, 25 Sep 2012 06:40:50 -0700	[thread overview]
Message-ID: <20120925134050.GC15419@kroah.com> (raw)
In-Reply-To: <50617DFB.3070405@atmel.com>

On Tue, Sep 25, 2012 at 11:48:43AM +0200, Nicolas Ferre wrote:
> On 09/24/2012 07:34 PM, Greg KH :
> > On Mon, Sep 24, 2012 at 09:44:31AM +0200, Nicolas Ferre wrote:
> >>> This patches fixed the issue by adding the gpio valid check.
> >>>
> >>> Signed-off-by: Joachim Eastwood <joachim.eastwood@jotron•com>
> >>
> >> Acked-by: Nicolas Ferre <nicolas.ferre@atmel•com>
> >>
> >> Thanks a *lot* Joachim for having chased this bug!
> >>
> >> Alan, Greg, this one is 3.6 last minute material... I Hope that it can
> >> make it!
> >>
> >>> ---
> >>>
> >>> Note: If 6fffb77c goes into stable please either include this patch also or
> >>> fold it into 6fffb77c to avoid regressions.
> >>
> >> Absolutely, I have tagged the faulty patch:
> >>     Cc: Stable <stable@vger•kernel.org> [3.4+]
> >>
> >> So it can be good if this one can follow the same path.
> > 
> > I'll queue this up for 3.7 and have it backported to 3.6.1 as it's a bit
> > late for 3.6 for me right now.
> 
> Ah, too bad! The kernel Oops may affect several AT91 SoC... Can't we
> push it with the help of Andrew Morton for late material?

3.6.1 is really too late for you?  What does one week buy you?

greg k-h

  reply	other threads:[~2012-09-25 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-23 20:56 [PATCH] USB: ohci-at91: fix null pointer in ohci_hcd_at91_overcurrent_irq Joachim Eastwood
2012-09-24  7:44 ` Nicolas Ferre
2012-09-24 17:34   ` Greg KH
2012-09-25  9:48     ` Nicolas Ferre
2012-09-25 13:40       ` Greg KH [this message]
2012-09-27  9:01         ` Nicolas Ferre
2012-09-27 16:17           ` Greg KH

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=20120925134050.GC15419@kroah.com \
    --to=gregkh@linuxfoundation$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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