From: Johan Meiring <johanmeiring@gmail.com>
To: gregkh@suse.de
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Johan Meiring <johanmeiring@gmail.com>
Subject: [PATCH 2/2] Staging: line6: fixed 80 character coding style issue in midibuf.c This is a patch to the midibuf.c file that fixes up an 80 character error thrown by the checkpatch.pl tool Signed-off-by: Johan Meiring <johanmeiring@gmail.com>
Date: Sun, 28 Mar 2010 21:36:38 +0200 [thread overview]
Message-ID: <1269804998-7169-1-git-send-email-johanmeiring@gmail.com> (raw)
---
drivers/staging/line6/midibuf.c | 9 ++++++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/line6/midibuf.c b/drivers/staging/line6/midibuf.c
index ab0a5f3..fb2658d 100644
--- a/drivers/staging/line6/midibuf.c
+++ b/drivers/staging/line6/midibuf.c
@@ -76,7 +76,8 @@ int midibuf_bytes_free(struct MidiBuffer *this)
return
midibuf_is_full(this) ?
0 :
- (this->pos_read - this->pos_write + this->size - 1) % this->size + 1;
+ (this->pos_read - this->pos_write + this->size - 1) % \
+ this->size + 1;
}
int midibuf_bytes_used(struct MidiBuffer *this)
@@ -84,7 +85,8 @@ int midibuf_bytes_used(struct MidiBuffer *this)
return
midibuf_is_empty(this) ?
0 :
- (this->pos_write - this->pos_read + this->size - 1) % this->size + 1;
+ (this->pos_write - this->pos_read + this->size - 1) % \
+ this->size + 1;
}
int midibuf_write(struct MidiBuffer *this, unsigned char *data, int length)
@@ -160,7 +162,8 @@ int midibuf_read(struct MidiBuffer *this, unsigned char *data, int length)
this->command_prev = command;
} else {
if (this->command_prev > 0) {
- int midi_length_prev = midibuf_message_length(this->command_prev);
+ int midi_length_prev = \
+ midibuf_message_length(this->command_prev);
if (midi_length_prev > 0) {
midi_length = midi_length_prev - 1;
--
1.6.3.3
next reply other threads:[~2010-03-28 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 19:36 Johan Meiring [this message]
2010-03-28 20:05 ` Joe Perches
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=1269804998-7169-1-git-send-email-johanmeiring@gmail.com \
--to=johanmeiring@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--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®