From: Arthur Moraes do Lago <arthurmoraeslago@gmail.com>
To: mchehab@kernel.org, gregkh@linuxfoundation.org,
mjpeg-users@lists.sourceforge.net, linux-media@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
lkcamp@lists.libreplanetbr.org
Subject: [PATCH] staging: media: zoran: fix trailing whitespaces
Date: Mon, 8 Apr 2019 01:55:54 -0300 [thread overview]
Message-ID: <20190408045554.18905-1-arthurmoraeslago@gmail.com> (raw)
There were several form feeds(^L) in the file, this patch removes them
to conform with the coding style.
Signed-off-by: Arthur Moraes do Lago <arthurmoraeslago@gmail.com>
---
Made a mistake while typing recipients on the last e-mail and it was not
sent to the kernel list. Re-sending now with correct address, sorry for
the hassle.
drivers/staging/media/zoran/videocodec.h | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/media/zoran/videocodec.h b/drivers/staging/media/zoran/videocodec.h
index 4946791fce0d..c37c0e4fb624 100644
--- a/drivers/staging/media/zoran/videocodec.h
+++ b/drivers/staging/media/zoran/videocodec.h
@@ -49,7 +49,7 @@
device dependent and vary between MJPEG/MPEG/WAVELET/... devices. (!!!!)
----------------------------------------------------------------------------
*/
-\f
+
/* ========================================== */
/* description of the videocodec_io structure */
@@ -96,7 +96,7 @@
the calls include frame numbers and flags (even/odd/...)
if needed and a flag which allows blocking until its ready
*/
-\f
+
/* ============== */
/* user interface */
/* ============== */
@@ -116,7 +116,7 @@ M zr36055[0] 0001 0000c001 00000000 (zr36050[0])
M zr36055[1] 0001 0000c001 00000000 (zr36050[1])
*/
-\f
+
/* =============================================== */
/* special defines for the videocodec_io structure */
@@ -195,7 +195,7 @@ M zr36055[1] 0001 0000c001 00000000 (zr36050[1])
/* -> used in get_image, put_image */
#define CODEC_TRANSFER_KERNEL 0 /* use "memcopy" */
#define CODEC_TRANSFER_USER 1 /* use "to/from_user" */
-\f
+
/* ========================= */
/* the structures itself ... */
@@ -309,7 +309,7 @@ struct videocodec_master {
__u16 reg,
__u32 value);
};
-\f
+
/* ================================================= */
/* function prototypes of the master/slave interface */
--
2.21.0
next reply other threads:[~2019-04-08 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 4:55 Arthur Moraes do Lago [this message]
[not found] <20190408043530.21594-1-arthurmoraeslago@gmail.com>
[not found] ` <20190408065103.GA6095@kadam>
2019-04-10 10:44 ` Hans Verkuil
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=20190408045554.18905-1-arthurmoraeslago@gmail.com \
--to=arthurmoraeslago@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=mchehab@kernel.org \
--cc=mjpeg-users@lists.sourceforge.net \
/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®