All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Scheller <d.scheller.oss@gmail.com>
To: linux-media@vger.kernel.org, mchehab@kernel.org,
	mchehab@s-opensource.com
Cc: jasmin@anw.at
Subject: [PATCH 0/3] staging/cxd2099: cosmetics, checkpatch fixup
Date: Tue, 12 Dec 2017 19:46:54 +0100	[thread overview]
Message-ID: <20171212184657.19730-1-d.scheller.oss@gmail.com> (raw)

From: Daniel Scheller <d.scheller@gmx.net>

These three small patches make the driver checkpatch-strict clean and
improves a few strings. No functional changes.

Essentially drivers/staging/media/cxd2099/ is now clean, esp.:

$ scripts/checkpatch.pl --strict --file drivers/staging/media/cxd2099/cxd2099.c
  total: 0 errors, 0 warnings, 0 checks, 705 lines checked

$ scripts/checkpatch.pl --strict --file drivers/staging/media/cxd2099/cxd2099.h
  total: 0 errors, 0 warnings, 0 checks, 45 lines checked

The three patches are the outcome of some bigger refactoring WIP.

Daniel Scheller (3):
  [media] staging/cxd2099: fix remaining checkpatch-strict issues
  [media] staging/cxd2099: fix debug message severity
  [media] staging/cxd2099: cosmetics: improve strings

 drivers/staging/media/cxd2099/cxd2099.c | 30 +++++++++++-------------------
 drivers/staging/media/cxd2099/cxd2099.h | 14 +++-----------
 2 files changed, 14 insertions(+), 30 deletions(-)

-- 
2.13.6

             reply	other threads:[~2017-12-12 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 18:46 Daniel Scheller [this message]
2017-12-12 18:46 ` [PATCH 1/3] [media] staging/cxd2099: fix remaining checkpatch-strict issues Daniel Scheller
2017-12-12 18:46 ` [PATCH 2/3] [media] staging/cxd2099: fix debug message severity Daniel Scheller
2017-12-12 18:46 ` [PATCH 3/3] [media] staging/cxd2099: cosmetics: improve strings Daniel Scheller

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=20171212184657.19730-1-d.scheller.oss@gmail.com \
    --to=d.scheller.oss@gmail.com \
    --cc=jasmin@anw.at \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mchehab@s-opensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.