From: "Marcos Canán" <mcanan@gmail.com>
To: gregkh@linuxfoundation.org
Cc: tapaswenipathak@gmail.com, josh@joshtriplett.org,
aedesymen@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, "Marcos Canán" <mcanan@gmail.com>
Subject: [PATCH] staging: wlan-ng: prism2fw: coding style: Fixed too long lines.
Date: Tue, 15 Sep 2015 20:09:54 -0300 [thread overview]
Message-ID: <1442358594-29077-1-git-send-email-mcanan@gmail.com> (raw)
This is a patch to the prism2fw.c file that fixes
too long lines.
Signed-off-by: Marcos Canán <mcanan@gmail.com>
---
drivers/staging/wlan-ng/prism2fw.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/wlan-ng/prism2fw.c b/drivers/staging/wlan-ng/prism2fw.c
index 9408644..42d75e74 100644
--- a/drivers/staging/wlan-ng/prism2fw.c
+++ b/drivers/staging/wlan-ng/prism2fw.c
@@ -708,7 +708,9 @@ static int plugimage(struct imgchunk *fchunk, unsigned int nfchunks,
continue;
}
- /* Validate plug address against chunk data and identify chunk */
+ /* Validate plug address against chunk data
+ * and identify chunk
+ */
for (c = 0; c < nfchunks; c++) {
cstart = fchunk[c].addr;
cend = fchunk[c].addr + fchunk[c].len;
@@ -923,7 +925,8 @@ static int read_fwfile(const struct ihex_binrec *record)
rcnt,
s3info[ns3info].len,
s3info[ns3info].type);
- if (((s3info[ns3info].len - 1) * sizeof(u16)) > sizeof(s3info[ns3info].info)) {
+ if (((s3info[ns3info].len - 1) * sizeof(u16)) >
+ sizeof(s3info[ns3info].info)) {
pr_err("S3 inforec length too long - aborting\n");
return 1;
}
--
1.7.10.4
next reply other threads:[~2015-09-15 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 23:09 Marcos Canán [this message]
2015-09-16 5:04 ` Sudip Mukherjee
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=1442358594-29077-1-git-send-email-mcanan@gmail.com \
--to=mcanan@gmail.com \
--cc=aedesymen@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tapaswenipathak@gmail.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
all inboxes | Powered by JetHome®