From: Leon Romanovsky <leon@leon.nu>
To: Andrey Utkin <andrey_utkin@fastmail.com>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bluecherry Maintainers <maintainers@bluecherrydvr.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Kalle Valo <kvalo@codeaurora.org>, Joe Perches <joe@perches.com>,
Jiri Slaby <jslaby@suse.com>,
devel@driverdev.osuosl.org, kernel-mentors@selenic.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH] Add tw5864 driver
Date: Thu, 17 Mar 2016 09:57:31 +0200 [thread overview]
Message-ID: <20160317075731.GC25216@leon.nu> (raw)
In-Reply-To: <1457920514-20792-1-git-send-email-andrey_utkin@fastmail.com>
On Mon, Mar 14, 2016 at 03:55:14AM +0200, Andrey Utkin wrote:
> From: Andrey Utkin <andrey.utkin@corp.bluecherry.net>
>
> Support for boards based on Techwell TW5864 chip which provides
> multichannel video & audio grabbing and encoding (H.264, MJPEG,
> ADPCM G.726).
>
> Signed-off-by: Andrey Utkin <andrey.utkin@corp.bluecherry.net>
> Tested-by: Andrey Utkin <andrey.utkin@corp.bluecherry.net>
> ---
> MAINTAINERS | 7 +
> drivers/staging/media/Kconfig | 2 +
> drivers/staging/media/Makefile | 1 +
> drivers/staging/media/tw5864/Kconfig | 11 +
> drivers/staging/media/tw5864/Makefile | 3 +
> drivers/staging/media/tw5864/tw5864-bs.h | 154 ++
> drivers/staging/media/tw5864/tw5864-config.c | 359 +++++
> drivers/staging/media/tw5864/tw5864-core.c | 453 ++++++
> drivers/staging/media/tw5864/tw5864-h264.c | 183 +++
> drivers/staging/media/tw5864/tw5864-reg.h | 2200 ++++++++++++++++++++++++++
> drivers/staging/media/tw5864/tw5864-tables.h | 237 +++
> drivers/staging/media/tw5864/tw5864-video.c | 1364 ++++++++++++++++
> drivers/staging/media/tw5864/tw5864.h | 280 ++++
> include/linux/pci_ids.h | 1 +
> 14 files changed, 5255 insertions(+)
> create mode 100644 drivers/staging/media/tw5864/Kconfig
> create mode 100644 drivers/staging/media/tw5864/Makefile
> create mode 100644 drivers/staging/media/tw5864/tw5864-bs.h
> create mode 100644 drivers/staging/media/tw5864/tw5864-config.c
> create mode 100644 drivers/staging/media/tw5864/tw5864-core.c
> create mode 100644 drivers/staging/media/tw5864/tw5864-h264.c
> create mode 100644 drivers/staging/media/tw5864/tw5864-reg.h
> create mode 100644 drivers/staging/media/tw5864/tw5864-tables.h
> create mode 100644 drivers/staging/media/tw5864/tw5864-video.c
> create mode 100644 drivers/staging/media/tw5864/tw5864.h
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 409509d..7bb1fa9 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11195,6 +11195,13 @@ T: git git://linuxtv.org/media_tree.git
> S: Odd fixes
> F: drivers/media/usb/tm6000/
>
> +TW5864 VIDEO4LINUX DRIVER
> +M: Bluecherry Maintainers <maintainers@bluecherrydvr.com>
I wonder if this the right thing to do. Generally speaking a maintainer is a
person and not a corporate.
> +M: Andrey Utkin <andrey.utkin@corp.bluecherry.net>
> +L: linux-media@vger.kernel.org
> +S: Supported
> +F: drivers/staging/media/tw5864/
<snip>
> +
> --- /dev/null
> +++ b/drivers/staging/media/tw5864/tw5864-bs.h
> @@ -0,0 +1,154 @@
> +/*
> + * TW5864 driver - Exp-Golomb code functions
> + *
> + * Copyright (C) 2015 Bluecherry, LLC <maintainers@bluecherrydvr.com>
> + * Author: Andrey Utkin <andrey.utkin@corp.bluecherry.net>
You don't need to state your name here. It is written in git log.
next prev parent reply other threads:[~2016-03-17 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 1:54 [PATCH] Add tw5864 driver - cover letter Andrey Utkin
2016-03-14 1:55 ` [PATCH] Add tw5864 driver Andrey Utkin
2016-03-14 2:24 ` Greg Kroah-Hartman
2016-03-14 3:32 ` Greg Kroah-Hartman
2016-03-15 14:07 ` Dan Carpenter
2016-03-17 7:57 ` Leon Romanovsky [this message]
2016-03-14 1:58 [PATCH] Add tw5864 driver - cover letter Andrey Utkin
2016-03-14 1:59 ` [PATCH] Add tw5864 driver Andrey Utkin
2016-03-14 2:07 ` Joe Perches
2016-03-14 8:06 ` Hans Verkuil
2016-03-14 11:15 ` Mauro Carvalho Chehab
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=20160317075731.GC25216@leon.nu \
--to=leon@leon.nu \
--cc=akpm@linux-foundation.org \
--cc=andrey_utkin@fastmail.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=jslaby@suse.com \
--cc=kernel-mentors@selenic.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maintainers@bluecherrydvr.com \
--cc=mchehab@osg.samsung.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 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.