public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jean Delvare <khali@linux-fr.org>,
	Douglas Landgraf <dougsland@gmail.com>
Cc: LMML <linux-media@vger.kernel.org>
Subject: Re: Status of the patches under review (29 patches)
Date: Wed, 24 Feb 2010 10:10:16 -0300	[thread overview]
Message-ID: <4B852538.2050207@redhat.com> (raw)
In-Reply-To: <20100224101807.60a468c3@hyperion.delvare>

Hi Jean,

Jean Delvare wrote:
 
> I have 3 patches pending which aren't in your list. I can see them in
> patchwork:
> 
> http://patchwork.kernel.org/patch/79755/
> http://patchwork.kernel.org/patch/79754/
> http://patchwork.kernel.org/patch/77349/
> 
> The former two are in "Accepted" state, and actually I received an
> e-mail telling me they had been accepted, however I can't see them in
> the hg repository. So where are they?

They are already on the git tree:

commit 2887117b31b77ebe5fb42f95ea8d77a3716b405b
Author: Jean Delvare <khali@linux-fr.org>
Date:   Tue Feb 16 14:22:37 2010 -0300

    V4L/DVB: bttv: Let the user disable IR support
    
    Add a new module parameter "disable_ir" to disable IR support. Several
    other drivers do that already, and this can be very handy for
    debugging purposes.
    
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

commit e151340a2a9e7147eb48114af0381122130266b0
Author: Jean Delvare <khali@linux-fr.org>
Date:   Fri Feb 19 00:18:41 2010 -0300

    V4L/DVB: bttv: Move I2C IR initialization
    
    Move I2C IR initialization from just after I2C bus setup to right
    before non-I2C IR initialization. This avoids the case where an I2C IR
    device is blocking audio support (at least the PV951 suffers from
    this). It is also more logical to group IR support together,
    regardless of the connectivity.
    
    This fixes bug #15184:
    http://bugzilla.kernel.org/show_bug.cgi?id=15184
    
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
    CC: stable@kernel.org
    Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

As patches in -hg are manually backported, maybe Douglas
haven't backported it yet or he simply missed.

Douglas, could you please check this?

> The latter is in "Not Applicable" state, and I have no idea what it
> means. The patch is really simple and I see no formatting issue. Should
> I just resend it?

This means that this patch is not applicable on -git. There's no versions.txt
upstream. All patches that don't have upstream code are marked as such on
patchwork. I generally ping Douglas on such cases, for him to double check on
-hg.

Anyway, the better is to c/c to Douglas on all patches that are meant only
to the building system.

Douglas, could you please check if you've applied this patch?

-- 

Cheers,
Mauro

  reply	other threads:[~2010-02-24 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24  5:40 Status of the patches under review (29 patches) Mauro Carvalho Chehab
2010-02-24  7:22 ` Guennadi Liakhovetski
2010-02-24 12:57   ` Mauro Carvalho Chehab
2010-02-24  9:18 ` Jean Delvare
2010-02-24 13:10   ` Mauro Carvalho Chehab [this message]
2010-02-25  9:59     ` Jean Delvare
2010-02-24 13:25 ` Andy Walls

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=4B852538.2050207@redhat.com \
    --to=mchehab@redhat.com \
    --cc=dougsland@gmail.com \
    --cc=khali@linux-fr.org \
    --cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox