Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756775Ab1CNPyG (ORCPT ); Mon, 14 Mar 2011 11:54:06 -0400 Received: from kroah.org ([198.145.64.141]:56723 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752130Ab1CNPyE (ORCPT ); Mon, 14 Mar 2011 11:54:04 -0400 Date: Mon, 14 Mar 2011 08:53:03 -0700 From: Greg KH To: Felipe Contreras Cc: omar.ramirez@ti.com, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, ohad@wizery.com, fernando.lugo@ti.com, tuomas@kulve.fi Subject: Re: [PATCH] staging: tidspbridge: protect dmm_map properly Message-ID: <20110314155303.GB5272@kroah.com> References: <1299889746-16502-1-git-send-email-omar.ramirez@ti.com> <20110312173626.GC24981@kroah.com> <20110313010633.GD20396@kroah.com> <1300116128-notmuch-felipe.contreras@nokia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1300116128-notmuch-felipe.contreras@nokia.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1933 Lines: 44 On Mon, Mar 14, 2011 at 05:33:09PM +0200, Felipe Contreras wrote: > greg@kroah.com wrote: > > On Sun, Mar 13, 2011 at 01:42:35AM +0200, Felipe Contreras wrote: > > > On Sat, Mar 12, 2011 at 7:36 PM, Greg KH wrote: > > > > 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? > > The reason is because it didn't seem like it was happening often, but > in Tuomas' case, it does so much it's basically unusable. So _now_ we > know this could have possibly been affecting many people we didn't know > about. > > You have to remember that this driver only started to work on .37, so > people might have tried it, seen it crashing and said "oh well, it's on > 'staging' for a reason", having no point of reference that would be a > valid conclusion, while in fact this is a regression from pre-staging > (the issue wasn't there). I understand you feeling like there is a rush here, but again, please recognize that we all have different priorities. The number of users out there using this driver is very small and again, this patch can safely wait until the first .38-stable release comes out. > Anyway, I don't think .38.1 is going to be released in one week, Is that a challenge? :) > but I guess if people are having issues and not reporting them, they > can wait more. Thanks, I think they can. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/