From: Deepak R Varma <drv@mailo.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, drv@mailo.com,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: [PATCH RESEND 0/5] staging: media: atomisp: code formatting changes
Date: Fri, 21 May 2021 00:30:41 +0530 [thread overview]
Message-ID: <cover.1619850663.git.drv@mailo.com> (raw)
Message-ID: <20210520190041.bMKyVs3f4nPpZrZrl6hYgapOqc3VzgrlkQ_xTH7lToc@z> (raw)
This patch set overall improves the code organisation and readability of
the files of atomisp drivers. There are several complaints reported by
checkpatch including ERROR and WARNING types on the files under atomisp/pci
directory.
The changes are proposed on a per file basis since there are many
issues to be addressed in each individual file. The patches are built
on the media_tree/for-v5.14-out1 tree/branch.
Deepak R Varma (5):
staging: media: atomisp: code formatting changes atomisp_csi2.c
staging: media: atomisp: code formatting changes sh_css_mipi.c
staging: media: atomisp: code formatting changes sh_css_params.c
staging: media: atomisp: code formatting changes sh_css_sp.c
staging: media: atomisp: code formatting changes sh_css_version.c
.../staging/media/atomisp/pci/atomisp_csi2.c | 72 +-
.../staging/media/atomisp/pci/sh_css_mipi.c | 170 ++--
.../staging/media/atomisp/pci/sh_css_params.c | 929 +++++++++---------
drivers/staging/media/atomisp/pci/sh_css_sp.c | 471 ++++-----
.../media/atomisp/pci/sh_css_version.c | 4 +-
5 files changed, 754 insertions(+), 892 deletions(-)
--
2.30.2
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2021-05-20 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 6:43 Deepak R Varma [this message]
2021-05-01 6:44 ` [PATCH 1/5] staging: media: atomisp: code formatting changes atomisp_csi2.c Deepak R Varma
2021-05-20 19:02 ` [PATCH RESEND " Deepak R Varma
2021-05-01 6:45 ` [PATCH 2/5] staging: media: atomisp: code formatting changes sh_css_mipi.c Deepak R Varma
2021-05-20 19:03 ` [PATCH RESEND " Deepak R Varma
2021-05-01 6:46 ` [PATCH 3/5] staging: media: atomisp: code formatting changes sh_css_params.c Deepak R Varma
2021-05-20 19:04 ` [PATCH RESEND " Deepak R Varma
2021-05-21 10:52 ` [PATCH " Dan Carpenter
2021-05-22 10:24 ` Deepak R Varma
2021-05-01 6:47 ` [PATCH 4/5] staging: media: atomisp: code formatting changes sh_css_sp.c Deepak R Varma
2021-05-20 19:05 ` [PATCH RESEND " Deepak R Varma
2021-05-01 6:48 ` [PATCH 5/5] staging: media: atomisp: code formatting changes sh_css_version.c Deepak R Varma
2021-05-20 19:06 ` [PATCH RESEND " Deepak R Varma
2021-05-20 19:00 ` [PATCH RESEND 0/5] staging: media: atomisp: code formatting changes Deepak R Varma
2021-06-12 16:43 ` Deepak R Varma
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.1619850663.git.drv@mailo.com \
--to=drv@mailo.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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 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).