From: Dan Carpenter <dan.carpenter@oracle.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Archana kumari <archanakumari959@gmail.com>
Subject: Re: [PATCH] [media] staging: media: Fix build for iMON LIRC driver
Date: Wed, 16 Oct 2013 10:03:40 +0300 [thread overview]
Message-ID: <20131016070340.GC11731@mwanda> (raw)
In-Reply-To: <1381845763-10487-3-git-send-email-treding@nvidia.com>
On Tue, Oct 15, 2013 at 04:02:43PM +0200, Thierry Reding wrote:
> Add a missing , between parameters in a call to dev_info().
>
Greg already reverted the original patch.
The original patch wasn't sent to the list. Archana, use
scripts/get_maintainer.pl to find out who to send patches to. Don't
CC the linux-kernel list though because they don't care about details in
staging.
regards,
dan carpenter
next prev parent reply other threads:[~2013-10-16 7:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 14:02 linux-next: Tree for Oct 15 Thierry Reding
2013-10-15 14:02 ` linux-next: manual merge of the trivial tree Thierry Reding
2013-10-16 9:12 ` Jozsef Kadlecsik
2013-10-16 9:20 ` Jiri Kosina
2013-10-16 14:56 ` Pablo Neira Ayuso
2013-10-16 20:10 ` Jozsef Kadlecsik
2013-10-15 14:02 ` [PATCH] [media] staging: media: Fix build for iMON LIRC driver Thierry Reding
2013-10-16 7:03 ` Dan Carpenter [this message]
2013-10-16 14:12 ` Greg Kroah-Hartman
2013-10-15 19:50 ` linux-next: Tree for Oct 15 (usb gadget f_mass_storage and storage_common) Randy Dunlap
2013-10-15 22:43 ` linux-next: Tree for Oct 15 (asymmetric keys) Randy Dunlap
2013-10-16 15:52 ` Thierry Reding
2013-10-19 17:07 ` Randy Dunlap
2013-10-16 5:21 ` linux-next: Tree for Oct 15 Guenter Roeck
2013-10-16 15:50 ` Thierry Reding
2013-10-16 16:37 ` Guenter Roeck
2013-10-16 16:43 ` Thierry Reding
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=20131016070340.GC11731@mwanda \
--to=dan.carpenter@oracle.com \
--cc=archanakumari959@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).