public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Omar Ramirez Luna <omar.ramirez@ti.com>,
	l-m <linux-kernel@vger.kernel.org>,
	Felipe Contreras <felipe.contreras@nokia.com>,
	l-o <linux-omap@vger.kernel.org>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Fernando Guzman Lugo <fernando.lugo@ti.com>,
	Tuomas Kulve <tuomas@kulve.fi>
Subject: Re: [PATCH] staging: tidspbridge: protect dmm_map properly
Date: Sat, 12 Mar 2011 17:06:33 -0800	[thread overview]
Message-ID: <20110313010633.GD20396@kroah.com> (raw)
In-Reply-To: <AANLkTinp0e4EiEH=XV9gCSJzoh-VAY-6qqs91x0s80ro@mail.gmail.com>

On Sun, Mar 13, 2011 at 01:42:35AM +0200, Felipe Contreras wrote:
> On Sat, Mar 12, 2011 at 7:36 PM, Greg KH <greg@kroah.com> wrote:
> > On Fri, Mar 11, 2011 at 06:29:06PM -0600, Omar Ramirez Luna wrote:
> >> Please consider to apply this patch in the staging tree, as the
> >> description says it fixes a crash in tidspbridge driver, this bug
> >> was already present but it seems to have surfaced by recent tests
> >> made by Felipe and Tuomas.
> >>
> >> It is an urgent fix for 2.6.38.
> >
> > Heh, it's funny to see such a "urgent" fix take so long to get to me :)
> 
> Well, depending on your hardware and use-case this might or might not
> be urgent. At least for some people the driver is unusable without
> this.

Urgency is all relative :)

> > Is it also applicable for .37?
> 
> Yes.

In the future, always say this so I don't have to ask please.

> > How about I send it to Linus for .39 and then add it to the .38-stable
> > tree when it comes out?
> 
> That was the plan for .38/.37-stable. I'd say that's fine, but it
> would be even better to avoid people getting bit by this on plain .38.

What is one more week, when you all waited months to get this to me?  In
other words, why should I suddenly now rush when no one else did?

I'll queue this up for .39 and mark it for stable inclusion.

thanks,

greg k-h

  reply	other threads:[~2011-03-13  1:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12  0:29 [PATCH] staging: tidspbridge: protect dmm_map properly Omar Ramirez Luna
2011-03-12 17:36 ` Greg KH
2011-03-12 23:42   ` Felipe Contreras
2011-03-13  1:06     ` Greg KH [this message]
2011-03-14 15:33       ` Felipe Contreras
2011-03-14 15:53         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2010-12-20 17:12 Felipe Contreras
2010-12-20 18:30 ` Kanigeri, Hari
2010-12-20 18:43   ` Felipe Contreras
2011-03-07 18:02 ` Felipe Contreras
2011-03-07 18:14   ` Ohad Ben-Cohen
2011-03-07 18:48   ` Greg KH
2011-03-07 19:29   ` Ramirez Luna, Omar
2011-03-07 21:48     ` Felipe Contreras

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=20110313010633.GD20396@kroah.com \
    --to=greg@kroah.com \
    --cc=felipe.contreras@gmail.com \
    --cc=felipe.contreras@nokia.com \
    --cc=fernando.lugo@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=omar.ramirez@ti.com \
    --cc=tuomas@kulve.fi \
    /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