From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org (open list:MEDIA INPUT
INFRASTRUCTURE (V4L/DVB))
Subject: [PATCH RFC 08/15] media: replace **** with a hug
Date: Fri, 30 Nov 2018 11:27:17 -0800 [thread overview]
Message-ID: <20181130192737.15053-9-jarkko.sakkinen@linux.intel.com> (raw)
In-Reply-To: <20181130192737.15053-1-jarkko.sakkinen@linux.intel.com>
In order to comply with the CoC, replace **** with a hug. In
addition, fix a coding style issue (lines with over 80 chars).
Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
---
drivers/media/i2c/bt819.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/media/i2c/bt819.c b/drivers/media/i2c/bt819.c
index 472e37637c8d..c0f198b764f0 100644
--- a/drivers/media/i2c/bt819.c
+++ b/drivers/media/i2c/bt819.c
@@ -165,9 +165,11 @@ static int bt819_init(struct v4l2_subdev *sd)
0x0f, 0x00, /* 0x0f Hue control */
0x12, 0x04, /* 0x12 Output Format */
0x13, 0x20, /* 0x13 Vertial Scaling msb 0x00
- chroma comb OFF, line drop scaling, interlace scaling
- BUG? Why does turning the chroma comb on fuck up color?
- Bug in the bt819 stepping on my board?
+ chroma comb OFF, line drop scaling,
+ interlace scaling BUG? Why does
+ turning the chroma comb on hug up
+ color? Bug in the bt819 stepping on
+ my board?
*/
0x14, 0x00, /* 0x14 Vertial Scaling lsb */
0x16, 0x07, /* 0x16 Video Timing Polarity
--
2.19.1
next prev parent reply other threads:[~2018-11-30 19:27 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181130192737.15053-1-jarkko.sakkinen@linux.intel.com>
2018-11-30 19:27 ` [PATCH RFC 01/15] MIPS: replace **** with a hug Jarkko Sakkinen
2018-11-30 19:57 ` Jarkko Sakkinen
2018-11-30 21:06 ` Nikolay Borisov
2018-11-30 21:50 ` Jarkko Sakkinen
2018-11-30 22:11 ` Nikolay Borisov
2018-11-30 21:13 ` Al Viro
2018-11-30 21:28 ` Randy Dunlap
2018-12-01 1:52 ` Joshua Kinard
2018-12-01 4:58 ` Mike Galbraith
2018-11-30 19:27 ` [PATCH RFC 02/15] Documentation: " Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 03/15] drm/nouveau: " Jarkko Sakkinen
2018-11-30 20:13 ` Diego Viola
2018-11-30 21:26 ` Jarkko Sakkinen
2018-11-30 22:03 ` Diego Viola
2018-11-30 19:27 ` [PATCH RFC 04/15] m68k: " Jarkko Sakkinen
2018-11-30 19:44 ` John Paul Adrian Glaubitz
2018-11-30 20:59 ` Jarkko Sakkinen
2018-11-30 21:59 ` Jiri Kosina
2018-11-30 19:27 ` [PATCH RFC 05/15] parisc: " Jarkko Sakkinen
2018-11-30 22:48 ` Dennis Clarke
2018-11-30 23:03 ` Jarkko Sakkinen
2018-11-30 23:05 ` Diego Viola
2018-11-30 19:27 ` [PATCH RFC 06/15] cpufreq: " Jarkko Sakkinen
2018-12-03 9:08 ` Rafael J. Wysocki
2018-11-30 19:27 ` [PATCH RFC 07/15] ide: " Jarkko Sakkinen
2018-11-30 19:27 ` Jarkko Sakkinen [this message]
2018-12-01 8:01 ` [PATCH RFC 08/15] media: " Tomasz Figa
2018-11-30 19:27 ` [PATCH RFC 09/15] mtd: " Jarkko Sakkinen
2018-11-30 19:39 ` Boris Brezillon
2018-11-30 20:56 ` Jarkko Sakkinen
2018-12-01 10:31 ` Richard Weinberger
2018-11-30 19:27 ` [PATCH RFC 10/15] net/sunhme: " Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 11/15] scsi: " Jarkko Sakkinen
2018-11-30 20:21 ` James Bottomley
2018-11-30 21:30 ` Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 12/15] inotify: " Jarkko Sakkinen
2018-12-01 6:40 ` Amir Goldstein
2018-12-05 9:49 ` Jan Kara
2018-11-30 19:27 ` [PATCH RFC 13/15] irq: " Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 14/15] lib: " Jarkko Sakkinen
2018-11-30 19:41 ` Steven Rostedt
2018-11-30 19:46 ` Jonathan Corbet
2018-11-30 19:49 ` Jiri Kosina
2018-11-30 20:59 ` Jarkko Sakkinen
2018-12-02 3:24 ` Sergey Senozhatsky
2018-12-02 21:34 ` Tobin C. Harding
2018-11-30 19:27 ` [PATCH RFC 15/15] net: " Jarkko Sakkinen
2018-12-03 10:15 ` Phil Sutter
2018-11-30 19:40 ` [PATCH RFC 00/15] Zero ****s, hugload of hugs <3 Kees Cook
2018-11-30 19:48 ` Fwd: " Kees Cook
2018-11-30 20:42 ` Aaro Koskinen
2018-11-30 19:56 ` Davidlohr Bueso
2018-11-30 20:12 ` Jens Axboe
2018-11-30 20:34 ` Michael Schmitz
2018-11-30 20:35 ` David Miller
[not found] ` <2007856.n5V9iKLVsV@eth7>
2018-11-30 20:42 ` David Miller
[not found] ` <2269948.6tYQeUj9R1@eth7>
2018-11-30 20:53 ` Steven Rostedt
2018-11-30 20:43 ` Steven Rostedt
2018-12-01 4:08 ` Jarkko Sakkinen
2018-11-30 21:42 ` Jarkko Sakkinen
2018-11-30 21:47 ` David Miller
2018-11-30 21:53 ` Jens Axboe
2018-11-30 20:34 ` David Miller
2018-11-30 20:55 ` Jarkko Sakkinen
2018-11-30 21:01 ` James Bottomley
2018-11-30 21:44 ` Jarkko Sakkinen
2018-11-30 21:48 ` David Miller
2018-11-30 21:54 ` Jarkko Sakkinen
2018-11-30 22:04 ` James Bottomley
2018-11-30 21:57 ` James Bottomley
2018-11-30 22:12 ` Jarkko Sakkinen
2018-11-30 22:14 ` Jonathan Corbet
2018-11-30 22:26 ` Jarkko Sakkinen
2018-11-30 22:29 ` Jarkko Sakkinen
2018-11-30 22:30 ` James Bottomley
2018-11-30 22:40 ` Jarkko Sakkinen
2018-11-30 23:28 ` Jarkko Sakkinen
2018-12-01 8:20 ` Geert Uytterhoeven
2018-12-07 13:39 ` Eric Curtin
2018-11-30 22:26 ` James Bottomley
2018-11-30 21:02 ` Steven Rostedt
2018-11-30 21:04 ` Jonathan Corbet
2018-11-30 19:57 ` Geert Uytterhoeven
2018-11-30 21:09 ` Jarkko Sakkinen
2018-11-30 20:09 ` John Paul Adrian Glaubitz
2018-11-30 21:32 ` Jarkko Sakkinen
2018-11-30 20:31 ` Matthias Brugger
2018-11-30 21:34 ` Jarkko Sakkinen
2018-11-30 21:07 ` Jarkko Sakkinen
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=20181130192737.15053-9-jarkko.sakkinen@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).