From: Riccardo Schirone <sirmy15@gmail.com>
To: alan@linux.intel.com, gregkh@linuxfoundation.org,
linux-media@vger.kernel.org
Cc: Riccardo Schirone <sirmy15@gmail.com>
Subject: [PATCH 0/4] fix some checkpatch style issues in atomisp driver
Date: Mon, 27 Nov 2017 22:44:09 +0100 [thread overview]
Message-ID: <20171127214413.10749-1-sirmy15@gmail.com> (raw)
This patch series fixes some coding style issues reported by checkpatch.
It is based on next-20171127.
Riccardo Schirone (4):
staging: add missing blank line after declarations in atomisp-ov5693
staging: improve comments usage in atomisp-ov5693
staging: improves comparisons readability in atomisp-ov5693
staging: fix indentation in atomisp-ov5693
.../media/atomisp/i2c/ov5693/atomisp-ov5693.c | 63 +++++++++++++++-------
1 file changed, 44 insertions(+), 19 deletions(-)
--
2.14.3
next reply other threads:[~2017-11-27 21:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 21:44 Riccardo Schirone [this message]
2017-11-27 21:44 ` [PATCH 1/4] staging: add missing blank line after declarations in atomisp-ov5693 Riccardo Schirone
2017-11-28 9:53 ` jacopo mondi
2017-11-28 10:36 ` Riccardo S.
2017-11-27 21:44 ` [PATCH 2/4] staging: improve comments usage " Riccardo Schirone
2017-11-27 21:44 ` [PATCH 3/4] staging: improves comparisons readability " Riccardo Schirone
2017-11-28 9:51 ` jacopo mondi
2017-11-27 21:44 ` [PATCH 4/4] staging: fix indentation " Riccardo Schirone
2017-11-28 20:40 ` [PATCHv2 0/4] fix some checkpatch style issues in atomisp driver Riccardo Schirone
2017-11-28 20:40 ` [PATCHv2 1/4] staging: add missing blank line after declarations in atomisp-ov5693 Riccardo Schirone
2017-11-28 20:40 ` [PATCHv2 2/4] staging: improve comments usage " Riccardo Schirone
2017-11-28 20:40 ` [PATCHv2 3/4] staging: improves comparisons readability " Riccardo Schirone
2017-11-28 20:40 ` [PATCHv2 4/4] staging: fix indentation " Riccardo Schirone
2017-11-29 8:40 ` [PATCHv2 0/4] fix some checkpatch style issues in atomisp driver Sakari Ailus
2017-11-29 9:07 ` Riccardo S.
2017-11-29 9:31 ` [PATCH " Riccardo S.
2017-11-29 10:09 ` jacopo mondi
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=20171127214413.10749-1-sirmy15@gmail.com \
--to=sirmy15@gmail.com \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-media@vger.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