From: Ritwik Sahani <ritwik.shn.dev@gmail.com>
Cc: Ritwik Sahani <ritwik.shn.dev@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH] media: atomisp: move trailing statements to next line
Date: Wed, 14 Sep 2022 00:59:32 +0530 [thread overview]
Message-ID: <20220913192933.31694-1-ritwik.shn.dev@gmail.com> (raw)
Adhere to Linux kernel coding style.
Reported by checkpatch:
ERROR: trailing statements should be on next line
Signed-off-by: Ritwik Sahani <ritwik.shn.dev@gmail.com>
---
.../hive_isp_css_common/host/input_system.c | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/media/atomisp/pci/hive_isp_css_common/host/input_system.c b/drivers/staging/media/atomisp/pci/hive_isp_css_common/host/input_system.c
index 712e01c37870..4b426d938586 100644
--- a/drivers/staging/media/atomisp/pci/hive_isp_css_common/host/input_system.c
+++ b/drivers/staging/media/atomisp/pci/hive_isp_css_common/host/input_system.c
@@ -878,7 +878,8 @@ static input_system_err_t input_system_configure_channel(
return INPUT_SYSTEM_ERR_PARAMETER_NOT_SUPPORTED;
}
- if (error != INPUT_SYSTEM_ERR_NO_ERROR) return error;
+ if (error != INPUT_SYSTEM_ERR_NO_ERROR)
+ return error;
// Input switch channel configurations must be combined in united config.
config.input_switch_cfg.hsync_data_reg[channel.source_cfg.csi_cfg.csi_port * 2]
=
@@ -1586,13 +1587,15 @@ static input_system_err_t input_system_configure_channel_sensor(
status = set_source_type(&config.source_type, channel.source_type,
&config.source_type_flags);
- if (status != INPUT_SYSTEM_ERR_NO_ERROR) return status;
+ if (status != INPUT_SYSTEM_ERR_NO_ERROR)
+ return status;
// Check for conflicts on source (implicitly on multicast, capture unit and input buffer).
status = set_csi_cfg(&config.csi_value[port], &channel.source_cfg.csi_cfg,
&config.csi_flags[port]);
- if (status != INPUT_SYSTEM_ERR_NO_ERROR) return status;
+ if (status != INPUT_SYSTEM_ERR_NO_ERROR)
+ return status;
switch (channel.source_cfg.csi_cfg.buffering_mode) {
case INPUT_SYSTEM_FIFO_CAPTURE:
@@ -1601,7 +1604,8 @@ static input_system_err_t input_system_configure_channel_sensor(
mux = INPUT_SYSTEM_MIPI_PORT0 + port;
status = input_system_multiplexer_cfg(&config.multiplexer, mux,
&config.multiplexer_flags);
- if (status != INPUT_SYSTEM_ERR_NO_ERROR) return status;
+ if (status != INPUT_SYSTEM_ERR_NO_ERROR)
+ return status;
config.multicast[port] = INPUT_SYSTEM_CSI_BACKEND;
// Shared resource, so it should be blocked.
@@ -1616,7 +1620,8 @@ static input_system_err_t input_system_configure_channel_sensor(
mux = INPUT_SYSTEM_ACQUISITION_UNIT;
status = input_system_multiplexer_cfg(&config.multiplexer, mux,
&config.multiplexer_flags);
- if (status != INPUT_SYSTEM_ERR_NO_ERROR) return status;
+ if (status != INPUT_SYSTEM_ERR_NO_ERROR)
+ return status;
config.multicast[port] = INPUT_SYSTEM_INPUT_BUFFER;
// Shared resource, so it should be blocked.
@@ -1631,7 +1636,8 @@ static input_system_err_t input_system_configure_channel_sensor(
mux = INPUT_SYSTEM_ACQUISITION_UNIT;
status = input_system_multiplexer_cfg(&config.multiplexer, mux,
&config.multiplexer_flags);
- if (status != INPUT_SYSTEM_ERR_NO_ERROR) return status;
+ if (status != INPUT_SYSTEM_ERR_NO_ERROR)
+ return status;
config.multicast[port] = INPUT_SYSTEM_INPUT_BUFFER;
// Shared resource, so it should be blocked.
--
2.34.1
reply other threads:[~2022-09-13 19:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220913192933.31694-1-ritwik.shn.dev@gmail.com \
--to=ritwik.shn.dev@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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