From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]:44011 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753293Ab0J0Rw0 (ORCPT ); Wed, 27 Oct 2010 13:52:26 -0400 Message-ID: <4CC866C9.2010803@redhat.com> Date: Wed, 27 Oct 2010 15:52:09 -0200 From: Mauro Carvalho Chehab MIME-Version: 1.0 To: Hans de Goede CC: Linus Torvalds , Andrew Morton , Linux Media Mailing List , Linux Kernel Mailing List Subject: Re: [GIT PULL for 2.6.37-rc1] V4L/DVB updates References: <4CC8380D.3040802@redhat.com> <4CC863D6.7010404@redhat.com> In-Reply-To: <4CC863D6.7010404@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-ID: Sender: Em 27-10-2010 15:39, Hans de Goede escreveu: > Hi, > > On 10/27/2010 04:32 PM, Mauro Carvalho Chehab wrote: >> Linus, >> >> Please pull from >> ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git v4l_for_linus >> > > > > I see that you did not include the changes from my pull request send today, > understandably so, but I wonder if these could still get into 2.6.37 for say > rc2 ? > > All of them are bug fixes except for the xirlink_cit button support which > makes changes to a driver new this cycle, so no chance for causing regressions > there. Before posting patches upstream, I send them to Linux-next in order to be tested there for a while, before sending pull requests upstream. So, yes, patches sent me recently will need to wait for the next series of patches. I can't tell you in advance if I'll merge them for rc2, as I didn't review them yet, and I'll be travelling abroad next week for LPC/KS, but bug fixes need to be addressed and merged in time for 2.6.37. Cheers, Mauro.