From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 0/8] Fix issues in em28xx
Date: Sat, 20 Dec 2014 15:10:04 +0100 [thread overview]
Message-ID: <5495833C.9080507@googlemail.com> (raw)
In-Reply-To: <20141220124448.GG11285@n2100.arm.linux.org.uk>
Am 20.12.2014 um 13:44 schrieb Russell King - ARM Linux:
> It isn't clear who is the maintainer for this driver; there is no
> MAINTAINERS entry. If there is a maintainer, please ensure that they
> add themselves to this critical file. Thanks.
(line 3598)
EM28XX VIDEO4LINUX DRIVER
M: Mauro Carvalho Chehab <m.chehab@samsung.com>
L: linux-media@vger.kernel.org
W: http://linuxtv.org
T: git git://linuxtv.org/media_tree.git
S: Maintained
F: drivers/media/usb/em28xx/
next prev parent reply other threads:[~2014-12-20 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 12:44 [PATCH 0/8] Fix issues in em28xx Russell King - ARM Linux
2014-12-20 12:45 ` [PATCH 1/8] [media] em28xx: fix em28xx-input removal Russell King
[not found] ` <549583AA.9040204@googlemail.com>
2014-12-20 14:51 ` Russell King - ARM Linux
2014-12-21 19:18 ` Frank Schäfer
2014-12-20 12:45 ` [PATCH 2/8] [media] em28xx: ensure "closing" messages terminate with a newline Russell King
2014-12-20 12:45 ` [PATCH 3/8] [media] em28xx-input: fix missing newlines Russell King
2014-12-20 12:45 ` [PATCH 4/8] [media] em28xx-core: " Russell King
2014-12-20 12:45 ` [PATCH 5/8] [media] em28xx-audio: " Russell King
2014-12-20 12:45 ` [PATCH 6/8] " Russell King
2014-12-20 12:45 ` [PATCH 7/8] [media] em28xx-dvb: " Russell King
2014-12-20 12:45 ` [PATCH 8/8] [media] em28xx-video: " Russell King
2014-12-20 14:10 ` Frank Schäfer [this message]
2014-12-20 14:53 ` [PATCH 0/8] Fix issues in em28xx Russell King - ARM Linux
2014-12-21 19:20 ` Frank Schäfer
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=5495833C.9080507@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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.