public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: HoP <jpetrous@gmail.com>
Cc: ajurik@quick.cz, linux-media@vger.kernel.org
Subject: Re: [PATCH v3] isl6421.c - added tone control and temporary diseqc overcurrent
Date: Wed, 20 Jan 2010 21:26:34 -0200	[thread overview]
Message-ID: <4B57912A.9000908@redhat.com> (raw)
In-Reply-To: <846899811001201443g60bd03edg9bd6fb5a4d3888a8@mail.gmail.com>

HoP wrote:
> Hi Mauro,
> 
> 2010/1/20 Mauro Carvalho Chehab <mchehab@redhat.com>:
>> HoP wrote:
>>> Hi Mauro,
>>>
>>> Not to hassle you, I'm sure you're very busy.
>>>
>>> But I'm not yet received a response from you on mail with corrected patch.
>>>
>>> Your attention would be appreciated
>> Hi Honza,
>>
>> The patch looks correct to me, but, as I previously mentioned, our policy is
>> to add new features at the kernel driver only together with a driver that
>> actually requires it. This helps to avoid increasing the kernel without need.
>>
>> So, please re-submit it when you have your driver requiring the isl6421
>> changes ready for submission, on the same patch series.
>>
> 
> Are you sure about such policy?
> 
> I did small google research and found out the following:
> 
> My feeling is different otherwise I don't understand why did you
> accept WITHOUT any word Oliver Endriss' PULL request
> from December 12th:
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg13302.html
> 
> I'm pointing on Oliver's pull request only because he did very similar
> thing for lnbp21 like I did for isl6421.
> 
> You very quickly added his patch to 2.6.33 on December 16th:
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg13429.html
> 
> So again. If I'm not blind you have accepted same work from him
> but not from me. Please show me what I have overlooked
> and this is not true.
> 
> Another possible explanation is that I'm totally unknow.
> 
> I hope you have some other explanation otherwise it feels to
> me like elitism.

As far as I understood, those changes are needed by the mantis driver, that
got committed on the next day, as shown at the commit logs:

http://linuxtv.org/hg/v4l-dvb/rev/07c36cb88bce
http://linuxtv.org/hg/v4l-dvb/rev/d644727cd528

So, on that time I had already a pull request for the mantis driver. 

It is fine if I receive two separate pull requests, one depending of the other.

That's said, Oliver is the maintainer of isl6421 driver, so he is the one that better 
know what bugs are there and what fixes are needed. Due to that, when I receive a 
patch from a driver maintainer, I'm inclined to ack with the changes, in the belief
that he is doing the better for the driver. Even so, I review the driver looking
for troubles on his approach taking more care with new exported symbols added and with
new userspace API's that the patch might have.

Cheers,
Mauro.

  reply	other threads:[~2010-01-20 23:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 15:49 [PATCH v2] isl6421.c - added tone control and temporary diseqc overcurrent HoP
2009-12-15 18:03 ` Mauro Carvalho Chehab
2009-12-16  0:20   ` [PATCH v3] " HoP
2010-01-20 13:58     ` HoP
2010-01-20 18:31       ` Mauro Carvalho Chehab
2010-01-20 22:43         ` HoP
2010-01-20 23:26           ` Mauro Carvalho Chehab [this message]
2010-01-20 23:59             ` HoP

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=4B57912A.9000908@redhat.com \
    --to=mchehab@redhat.com \
    --cc=ajurik@quick.cz \
    --cc=jpetrous@gmail.com \
    --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