public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: m-karicheri2@ti.com
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH v3 1/6] V4L - vpfe capture - header files for ISIF driver
Date: Mon, 01 Feb 2010 21:12:03 -0200	[thread overview]
Message-ID: <4B675FC3.2050505@redhat.com> (raw)
In-Reply-To: <1265063238-29072-3-git-send-email-m-karicheri2@ti.com>

m-karicheri2@ti.com wrote:
> From: Murali Karicheri <m-karicheri2@ti.com>
> 
> This is the header file for ISIF driver on DM365.  ISIF driver is equivalent
> to CCDC driver on DM355 and DM644x. This driver is tested for
> YUV capture from TVP514x driver. This patch contains the header files required for
> this driver. The name of the file is changed to reflect the name of IP.
> 
> Reviewed-by: Nori, Sekhar <nsekhar@ti.com>
> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl>
> 
> Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl> 
> Signed-off-by: Muralidharan Karicheri <m-karicheri2@ti.com>
> ---
> Applies to linux-next tree of v4l-dvb
>  - rebasing to latest for merge (v3) 
>  - Updated based on comments against v1 of the patch (v2)
>  drivers/media/video/davinci/isif_regs.h |  269 ++++++++++++++++
>  include/media/davinci/isif.h            |  531 +++++++++++++++++++++++++++++++
>  2 files changed, 800 insertions(+), 0 deletions(-)
>  create mode 100644 drivers/media/video/davinci/isif_regs.h
>  create mode 100644 include/media/davinci/isif.h

Hi Murali,

As always, it is almost impossible for me to know if you're submitting yet another RFC version
or a final version to be applied.

So, I kindly ask you to send all those patches that are still under discussions with [RFC PATCH]
at the subject, and, on the final version, send it to me via a git pull request.

Unfortunately, I don't have enough time to go inside every RFC patch that are under discussion,
so I prefer to optimize my time focusing on the patch versions that are considered ready for
inclusion, and where there's no c/c to any members-only ML.

-- 

Cheers,
Mauro

  parent reply	other threads:[~2010-02-01 23:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 22:27 [PATCH v3 6/6] DaVinci - Adding platform & board changes for vpfe capture on DM365 m-karicheri2
2010-02-01 22:27 ` [PATCH v3 5/6] V4L - vpfe capture - build environment for isif driver m-karicheri2
2010-02-01 22:27   ` [PATCH v3 1/6] V4L - vpfe capture - header files for ISIF driver m-karicheri2
2010-02-01 22:27     ` [PATCH v3 2/6] V4L - vpfe capture - source for ISIF driver on DM365 m-karicheri2
2010-02-01 22:27       ` [PATCH v3 3/6] V4L - vpfe capture - vpss driver enhancements for DM365 m-karicheri2
2010-02-01 22:27         ` [PATCH v3 4/6] V4L - vpfe_capture - bug fixes and enhancements m-karicheri2
2010-02-01 22:33     ` [PATCH v3 1/6] V4L - vpfe capture - header files for ISIF driver Karicheri, Muralidharan
2010-02-01 23:12     ` Mauro Carvalho Chehab [this message]
2010-02-02 15:50       ` Karicheri, Muralidharan
2010-02-02 17:10         ` Mauro Carvalho Chehab
2010-02-02 17:50           ` Karicheri, Muralidharan
2010-02-02 18:01             ` Mauro Carvalho Chehab
2010-02-03 17:34 ` [PATCH v3 6/6] DaVinci - Adding platform & board changes for vpfe capture on DM365 Karicheri, Muralidharan

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=4B675FC3.2050505@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=m-karicheri2@ti.com \
    /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