All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] [media] mantis: merge both vp2033 and vp2040 drivers
Date: Mon, 06 Aug 2012 17:20:43 -0300	[thread overview]
Message-ID: <5020271B.1020702@redhat.com> (raw)
In-Reply-To: <CAHFNz9Jz5x8i7-ip9BOdwC06tYR1SETctvvTpA4V=mbezhRoAw@mail.gmail.com>

Em 06-08-2012 17:07, Manu Abraham escreveu:
> On Tue, Aug 7, 2012 at 12:32 AM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>> As noticed at:
>>         http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/48034
>>
>> Both drivers are identical, except for the name. So, there's no
>> sense on keeping both. Instead of forking the entire code, just
>> fork the vp3033_config struct, saving some space, and cleaning
>> up the Kernel.
> 
>>
>> Reported-by: Igor M. Liplianin <liplianin@me.by>
>> Cc: Manu Abraham <abraham.manu@gmail.com>
>> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
> 
> Nack.
> 
> VP-2033 and 2040 are both different in terms of hardware. If someone
> wants to add
> in additional frontend characteristic differences, he shouldn't have
> to add in this code
> again.

The code are just the same for both! If it ever become different, then
it could be forked again, but for now, it is just duplicating the same
code on both places and wasting 200 lines of useless code.

Mauro.


  reply	other threads:[~2012-08-06 20:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 19:02 [PATCH] [media] mantis: merge both vp2033 and vp2040 drivers Mauro Carvalho Chehab
2012-08-06 20:07 ` Manu Abraham
2012-08-06 20:20   ` Mauro Carvalho Chehab [this message]
2012-08-06 20:27     ` Manu Abraham
2012-08-16 13:21       ` Bjørn Mork

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=5020271B.1020702@redhat.com \
    --to=mchehab@redhat.com \
    --cc=abraham.manu@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 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.