public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Marrero <jmarrero@gmail.com>
To: mchehab@osg.samsung.com
Cc: linux-media@vger.kernel.org
Subject: [PATCH] This patch fixes the following WARNING: Block comments use * on the subsequent lines This WARNING was found using the checkpatch tool.
Date: Wed, 25 Nov 2015 22:38:43 +0000	[thread overview]
Message-ID: <20151125223843.GA2356@localhost.localdomain> (raw)

[PATCH] This patch fixes the following WARNING: 
Block comments use * on the subsequent lines This WARNING was found using the checkpatch tool.

This is my third patch submition, I am following the kernel newbies website. 
While these patches are very basic any feedback is highly apreciated as I would like to continue
to contribute cleanups like this until I learn the process well and feel confortable to move 
into code changes beyond the warnings. 

Thank you in advance.

Signed-off-by: Joseph Marrero <jmarrero@gmail.com>
---
 drivers/staging/media/davinci_vpfe/davinci_vpfe_user.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/media/davinci_vpfe/davinci_vpfe_user.h b/drivers/staging/media/davinci_vpfe/davinci_vpfe_user.h
index 7b7e7b2..3cc9be7 100644
--- a/drivers/staging/media/davinci_vpfe/davinci_vpfe_user.h
+++ b/drivers/staging/media/davinci_vpfe/davinci_vpfe_user.h
@@ -538,7 +538,7 @@ struct vpfe_isif_raw_config {
 };
 
 /**********************************************************************
-      IPIPE API Structures
+*      IPIPE API Structures
 **********************************************************************/
 
 /* IPIPE module configurations */
-- 
2.5.0


                 reply	other threads:[~2015-11-25 22:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20151125223843.GA2356@localhost.localdomain \
    --to=jmarrero@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox