From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Mason <jdmason@kudzu.us>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging/dt3155v4l: use PCI_VENDOR_ID_INTEL
Date: Mon, 24 Feb 2014 16:17:12 -0800 [thread overview]
Message-ID: <20140225001712.GA27103@kroah.com> (raw)
In-Reply-To: <1393272500-1862-1-git-send-email-jdmason@kudzu.us>
On Mon, Feb 24, 2014 at 01:08:19PM -0700, Jon Mason wrote:
> Use PCI_VENDOR_ID_INTEL instead of creating its own vendor ID #define.
>
> Signed-off-by: Jon Mason <jdmason@kudzu.us>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> drivers/staging/media/dt3155v4l/dt3155v4l.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
$ ./scripts/get_maintainer.pl --file drivers/staging/media/dt3155v4l/dt3155v4l.c
Mauro Carvalho Chehab <m.chehab@samsung.com> (maintainer:MEDIA INPUT INFRA...,commit_signer:5/6=83%)
Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:STAGING SUBSYSTEM,commit_signer:1/6=17%)
Hans Verkuil <hans.verkuil@cisco.com> (commit_signer:5/6=83%,authored:4/6=67%,added_lines:7/9=78%,removed_lines:5/10=50%)
Jingoo Han <jg1.han@samsung.com> (commit_signer:1/6=17%,authored:1/6=17%,added_lines:1/9=11%,removed_lines:1/10=10%)
"Lad, Prabhakar" <prabhakar.csengg@gmail.com> (commit_signer:1/6=17%)
Russell King <rmk+kernel@arm.linux.org.uk> (authored:1/6=17%,added_lines:1/9=11%,removed_lines:4/10=40%)
linux-media@vger.kernel.org (open list:MEDIA INPUT INFRA...)
devel@driverdev.osuosl.org (open list:STAGING SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
I am not the person to send this to, please use the tools we have to
determine who to send patches to so they can get properly applied.
thanks,
greg k-h
prev parent reply other threads:[~2014-02-25 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 20:08 Jon Mason
2014-02-24 20:08 ` [PATCH 2/2] staging/rtl8192e: Remove unused code Jon Mason
2014-02-25 0:17 ` Greg Kroah-Hartman [this message]
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=20140225001712.GA27103@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®