linux-kernel - Re: [GIT PULL for 2.6.37-rc1] V4L/DVB updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 27 Oct 2010 15:52:09 -0200
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Hans de Goede <hdegoede@...hat.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Media Mailing List <linux-media@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL for 2.6.37-rc1] V4L/DVB updates

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
>>
> 
> <snip snip>
> 
> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/