From: Quytelda Kahja <quytelda@tamalin.org>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, chris@engineersdelight.de,
linux-kernel@vger.kernel.org, Michael.Fabry@microchip.com,
christian.gromm@microchip.com,
Quytelda Kahja <quytelda@tamalin.org>
Subject: [PATCH 2/2] staging: most: Fix a coding style problem
Date: Thu, 1 Mar 2018 18:11:44 -0800 [thread overview]
Message-ID: <20180302021144.10795-2-quytelda@tamalin.org> (raw)
In-Reply-To: <20180302021144.10795-1-quytelda@tamalin.org>
Indent the parameters for a function call that extends past 80 characters.
Signed-off-by: Quytelda Kahja <quytelda@tamalin.org>
---
drivers/staging/most/core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/most/core.c b/drivers/staging/most/core.c
index 67e2d7f29967..8d311970225e 100644
--- a/drivers/staging/most/core.c
+++ b/drivers/staging/most/core.c
@@ -1473,7 +1473,8 @@ void most_deregister_interface(struct most_interface *iface)
int i;
struct most_channel *c;
- pr_info("deregistering device %s (%s)\n", dev_name(&iface->dev), iface->description);
+ pr_info("deregistering device %s (%s)\n", dev_name(&iface->dev),
+ iface->description);
for (i = 0; i < iface->num_channels; i++) {
c = iface->p->channel[i];
if (c->pipe0.comp)
--
2.16.2
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-03-02 2:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 7:58 [PATCH 1/4] staging: most: Fix coding style problems Quytelda Kahja
2018-02-24 7:58 ` [PATCH 2/4] staging: most: Replace calls to BUG_ON() with WARN_ONCE() and return Quytelda Kahja
2018-03-01 16:21 ` Greg KH
2018-03-06 9:23 ` Quytelda Kahja
2018-03-06 9:47 ` Dan Carpenter
2018-03-07 1:31 ` [PATCH] staging: most: Remove unnecessary usage of BUG_ON() Quytelda Kahja
2018-03-07 8:37 ` Christian Gromm
2018-02-24 7:58 ` [PATCH 3/4] staging: most: Remove unnecessary OOM messages Quytelda Kahja
2018-02-24 7:58 ` [PATCH 4/4] staging: most: Fix missing identifier in function definition argument Quytelda Kahja
2018-03-01 16:20 ` [PATCH 1/4] staging: most: Fix coding style problems Greg KH
2018-03-02 2:11 ` [PATCH 1/2] staging: most: Fix a coding style problem Quytelda Kahja
2018-03-02 2:11 ` Quytelda Kahja [this message]
2018-03-02 10:12 ` [PATCH 2/2] " Dan Carpenter
2018-03-06 9:18 ` [PATCH v2 1/2] staging: most: Add a blank line Quytelda Kahja
2018-03-06 9:34 ` [PATCH v2 2/2] staging: most: Indent function parameter Quytelda Kahja
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=20180302021144.10795-2-quytelda@tamalin.org \
--to=quytelda@tamalin.org \
--cc=Michael.Fabry@microchip.com \
--cc=chris@engineersdelight.de \
--cc=christian.gromm@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®