From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Lad Prabhakar <prabhakar.csengg@gmail.com>
Cc: DLOS <davinci-linux-open-source@linux.davincidsp.com>,
LMML <linux-media@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH 1/7] media: davinci: vpif: remove unwanted header includes
Date: Thu, 16 May 2013 15:02:54 +0200 [thread overview]
Message-ID: <1561290.MnyCnpJz5W@avalon> (raw)
In-Reply-To: <1368709102-2854-2-git-send-email-prabhakar.csengg@gmail.com>
Hi Prabhakar,
Thank you for the patch.
On Thursday 16 May 2013 18:28:16 Lad Prabhakar wrote:
> From: Lad, Prabhakar <prabhakar.csengg@gmail.com>
>
> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com>
> ---
> drivers/media/platform/davinci/vpif.c | 7 -------
> 1 files changed, 0 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/media/platform/davinci/vpif.c
> b/drivers/media/platform/davinci/vpif.c index ea82a8b..d354d50 100644
> --- a/drivers/media/platform/davinci/vpif.c
> +++ b/drivers/media/platform/davinci/vpif.c
> @@ -17,18 +17,11 @@
> * GNU General Public License for more details.
> */
>
> -#include <linux/init.h>
> #include <linux/module.h>
> #include <linux/platform_device.h>
> -#include <linux/spinlock.h>
> -#include <linux/kernel.h>
> -#include <linux/io.h>
> -#include <linux/err.h>
> #include <linux/pm_runtime.h>
> #include <linux/v4l2-dv-timings.h>
I think you should keep most of those includes. For instance this file uses
spinlock functions, so linux/spinlock.h should be included. It might work fine
now due to nested includes, but if someone reorganizes the kernel headers
internal includes then the driver might break. As a general rule of good
practice you should include headers for all the APIs you use.
>
> -#include <mach/hardware.h>
> -
> #include "vpif.h"
>
> MODULE_DESCRIPTION("TI DaVinci Video Port Interface driver");
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-05-16 13:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 12:58 [PATCH 0/7] media: davinci: vpif trivial cleanup Lad Prabhakar
2013-05-16 12:58 ` [PATCH 1/7] media: davinci: vpif: remove unwanted header includes Lad Prabhakar
2013-05-16 13:02 ` Laurent Pinchart [this message]
2013-05-17 5:10 ` Prabhakar Lad
2013-05-17 9:58 ` Laurent Pinchart
2013-05-16 12:58 ` [PATCH 2/7] media: davinci: vpif: Convert to devm_* api Lad Prabhakar
2013-05-16 12:58 ` [PATCH 3/7] media: davinci: vpif: remove unnecessary braces around defines Lad Prabhakar
2013-05-16 12:58 ` [PATCH 4/7] media: davinci: vpif_capture: remove unwanted header inclusion and sort them alphabetically Lad Prabhakar
2013-05-16 12:58 ` [PATCH 5/7] media: davinci: vpif_capture: Convert to devm_* api Lad Prabhakar
2013-05-16 12:58 ` [PATCH 6/7] media: davinci: vpif_display: remove unwanted header inclusion and sort them alphabetically Lad Prabhakar
2013-05-16 12:58 ` [PATCH 7/7] media: davinci: vpif_display: Convert to devm_* api Lad Prabhakar
2013-05-23 9:38 ` [PATCH 0/7] media: davinci: vpif trivial cleanup Hans Verkuil
2013-05-23 9:40 ` Prabhakar Lad
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=1561290.MnyCnpJz5W@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=prabhakar.csengg@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