linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: [PATCH 00/11] em28xx: coding style improvements
Date: Sat,  3 Mar 2018 17:51:01 -0300	[thread overview]
Message-ID: <cover.1520110127.git.mchehab@s-opensource.com> (raw)

As there are significant changes on em28xx-cards and em28xx-dvb,
take some time to solve coding style issues there.

This series contain only "cosmetic" changes, although there is
a non-trivial change at em28xx-cards, making its probe function
easier to read.

Anyway, no behavior changes should be noticed after this
patch series.

Mauro Carvalho Chehab (11):
  em28xx: Add SPDX license tags where needed
  em28xx.h: Fix most coding style issues
  media: em28xx-reg.h: Fix coding style issues
  media: em28xx-audio: fix coding style issues
  media: em28xx-camera: fix coding style issues
  media: em28xx-cards: fix most coding style issues
  media:: rework the em28xx probing code
  media: em28xx-core: fix most coding style issues
  media: em28xx-i2c: fix most coding style issues
  media: em28xx-input: fix most coding style issues
  media: em28xx-video: fix most coding style issues

 drivers/media/usb/em28xx/em28xx-audio.c  | 116 +++---
 drivers/media/usb/em28xx/em28xx-camera.c |  49 ++-
 drivers/media/usb/em28xx/em28xx-cards.c  | 594 +++++++++++++++++--------------
 drivers/media/usb/em28xx/em28xx-core.c   | 128 ++++---
 drivers/media/usb/em28xx/em28xx-dvb.c    |  46 +--
 drivers/media/usb/em28xx/em28xx-i2c.c    | 131 +++----
 drivers/media/usb/em28xx/em28xx-input.c  | 163 +++++----
 drivers/media/usb/em28xx/em28xx-reg.h    |  50 +--
 drivers/media/usb/em28xx/em28xx-v4l.h    |  27 +-
 drivers/media/usb/em28xx/em28xx-vbi.c    |  39 +-
 drivers/media/usb/em28xx/em28xx-video.c  | 329 +++++++++--------
 drivers/media/usb/em28xx/em28xx.h        | 338 ++++++++++--------
 12 files changed, 1096 insertions(+), 914 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-03-03 20:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03 20:51 Mauro Carvalho Chehab [this message]
2018-03-03 20:51 ` [PATCH 01/11] em28xx: Add SPDX license tags where needed Mauro Carvalho Chehab
2018-03-03 20:51 ` [PATCH 02/11] em28xx.h: Fix most coding style issues Mauro Carvalho Chehab
2018-03-03 20:51 ` [PATCH 03/11] media: em28xx-reg.h: Fix " Mauro Carvalho Chehab
2018-03-03 20:51 ` [PATCH 04/11] media: em28xx-audio: fix " Mauro Carvalho Chehab
2018-03-03 20:51 ` [PATCH 05/11] media: em28xx-camera: " Mauro Carvalho Chehab
2018-03-03 20:51 ` [PATCH 06/11] media: em28xx-cards: fix most " Mauro Carvalho Chehab
2018-03-03 20:51 ` [PATCH 07/11] media: em28xx-cards: rework the em28xx probing code Mauro Carvalho Chehab
2018-03-03 20:51 ` [PATCH 08/11] media: em28xx-core: fix most coding style issues Mauro Carvalho Chehab
2018-03-03 20:51 ` [PATCH 09/11] media: em28xx-i2c: " Mauro Carvalho Chehab
2018-03-03 20:51 ` [PATCH 10/11] media: em28xx-input: " Mauro Carvalho Chehab
2018-03-03 20:51 ` [PATCH 11/11] media: em28xx-video: " Mauro Carvalho Chehab

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=cover.1520110127.git.mchehab@s-opensource.com \
    --to=mchehab@s-opensource.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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).