All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@linux.intel.com>
To: greg@kroah.com, linux-media@vger.kernel.org
Subject: [PATCH 05/14] staging: atomisp: move mipi_info assignment to next line in __get_asd_from_port()
Date: Wed, 12 Apr 2017 19:20:49 +0100	[thread overview]
Message-ID: <149202124311.16615.12039964731095677270.stgit@acox1-desk1.ger.corp.intel.com> (raw)
In-Reply-To: <149202119790.16615.4841216953457109397.stgit@acox1-desk1.ger.corp.intel.com>

From: Daeseok Youn <daeseok.youn@gmail.com>

The line which is initializing mipi_info variable is too long
to read. It would be placed in next line.

Signed-off-by: Daeseok Youn <daeseok.youn@gmail.com>
Signed-off-by: Alan Cox <alan@linux.intel.com>
---
 .../media/atomisp/pci/atomisp2/atomisp_cmd.c       |    8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/drivers/staging/media/atomisp/pci/atomisp2/atomisp_cmd.c b/drivers/staging/media/atomisp/pci/atomisp2/atomisp_cmd.c
index d98a6ea..a8614a9 100644
--- a/drivers/staging/media/atomisp/pci/atomisp2/atomisp_cmd.c
+++ b/drivers/staging/media/atomisp/pci/atomisp2/atomisp_cmd.c
@@ -533,9 +533,11 @@ __get_asd_from_port(struct atomisp_device *isp, mipi_port_ID_t port)
 	/* Check which isp subdev to send eof */
 	for (i = 0; i < isp->num_of_streams; i++) {
 		struct atomisp_sub_device *asd = &isp->asd[i];
-		struct camera_mipi_info *mipi_info =
-				atomisp_to_sensor_mipi_info(
-					isp->inputs[asd->input_curr].camera);
+		struct camera_mipi_info *mipi_info;
+
+		mipi_info = atomisp_to_sensor_mipi_info(
+				isp->inputs[asd->input_curr].camera);
+
 		if (asd->streaming == ATOMISP_DEVICE_STREAMING_ENABLED &&
 		    __get_mipi_port(isp, mipi_info->port) == port) {
 			return asd;

  parent reply	other threads:[~2017-04-12 18:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 18:20 [PATCH 01/14] staging: atomisp: use local variable to reduce number of references Alan Cox
2017-04-12 18:20 ` [PATCH 02/14] staging/atomisp: fix spelling mistake: "falied" -> "failed" Alan Cox
2017-04-12 18:20 ` [PATCH 03/14] staging: atomisp: remove enable_isp_irq function and add disable_isp_irq Alan Cox
2017-04-12 18:20 ` [PATCH 04/14] staging: atomisp: replace "&isp->asd[i]" with "asd" in __get_asd_from_port() Alan Cox
2017-04-12 18:20 ` Alan Cox [this message]
2017-04-12 18:21 ` [PATCH 06/14] atomisp: remove most of the uses of atomisp_kernel_malloc Alan Cox
2017-04-12 18:21 ` [PATCH 07/14] atomisp: unwrap the _ex malloc/free functions Alan Cox
2017-04-12 18:21 ` [PATCH 08/14] atomisp: remove indirection from sh_css_malloc Alan Cox
2017-04-12 18:21 ` [PATCH 09/14] atomisp: remove sh_css_malloc indirections where we can Alan Cox
2017-04-12 18:21 ` [PATCH 10/14] atomisp: remove contiguous handling Alan Cox
2017-04-12 18:22 ` [PATCH 11/14] atomisp: remove satm kernel Alan Cox
2017-04-12 18:22 ` [PATCH 12/14] atomisp: remove fixedbds kernel code Alan Cox
2017-04-13 11:53   ` kbuild test robot
2017-04-14  8:09     ` Greg KH
2017-04-12 18:22 ` [PATCH 13/14] atomisp: remove xnr3_0_5 and xnr3_0_11 Alan Cox
2017-04-12 18:22 ` [PATCH 14/14] atomisp: remove UDS kernel code Alan Cox
2017-04-13 19:27   ` kbuild test robot
2017-04-14  8:11     ` Greg KH

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=149202124311.16615.12039964731095677270.stgit@acox1-desk1.ger.corp.intel.com \
    --to=alan@linux.intel.com \
    --cc=greg@kroah.com \
    --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 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.