All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL for 2.6.37-rc1] V4L/DVB updates
Date: Wed, 27 Oct 2010 15:52:09 -0200	[thread overview]
Message-ID: <4CC866C9.2010803@redhat.com> (raw)
In-Reply-To: <4CC863D6.7010404@redhat.com>

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.

      reply	other threads:[~2010-10-27 17:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 14:32 [GIT PULL for 2.6.37-rc1] V4L/DVB updates Mauro Carvalho Chehab
2010-10-27 15:30 ` Jiri Slaby
2010-10-27 15:41   ` Mauro Carvalho Chehab
2010-10-27 15:48     ` Devin Heitmueller
2010-10-27 16:46       ` Mauro Carvalho Chehab
2010-10-27 17:52         ` Devin Heitmueller
2010-10-27 15:53     ` Jiri Slaby
2010-10-27 16:36       ` Mauro Carvalho Chehab
2010-10-27 16:38         ` Jiri Slaby
2010-10-27 16:52           ` Mauro Carvalho Chehab
2010-10-27 17:39 ` Hans de Goede
2010-10-27 17:52   ` Mauro Carvalho Chehab [this message]

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=4CC866C9.2010803@redhat.com \
    --to=mchehab@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.