Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Kicherer <dev@kicherer.org>
To: Daniel Mack <daniel@zonque.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] MIDI driver for Behringer BCD2000 USB device
Date: Wed, 05 Feb 2014 16:33:36 +0100	[thread overview]
Message-ID: <52F259D0.9070705@kicherer.org> (raw)
In-Reply-To: <52F2184D.9060209@zonque.org>


Hi Daniel,

thank you very much for your comments! I hope I fixed most of the
points but I also have a few questions/comments:

On 05.02.2014 11:54, Daniel Mack wrote:
>> +#ifdef CONFIG_USB_DEBUG
>> +#define DEBUG	1
>> +#else
>> +#define DEBUG	0
>> +#endif
>
> Please use the define directly instead of introducing a new one.

I replaced it with:

#ifndef CONFIG_USB_DEBUG
#define CONFIG_USB_DEBUG 0
#endif

As it can be undefined. I hope that's okay.

> Your patch has a huge number of style issues, which
> scripts/checkpatch.pl will point you to. I got:

Interesting, I copied many issues from other modules. :)
If fixed most of them except these:

WARNING: quoted string split across lines
#310: FILE: sound/usb/bcd2000/bcd2000.c:254:
+                       "bcd2000_midi_send(%p): usb_submit_urb() failed"
+                       "ret=%d, len=%d\n", substream, ret, len);

WARNING: quoted string split across lines
#392: FILE: sound/usb/bcd2000/bcd2000.c:336:
+                               "bcd2000_init_device: usb_submit_urb() 
failed,"
+                               "ret=%d: ", ret);

I don't know how to avoid them, as all strings in one line would be
longer than 80 characters.

>> +		/* determine the number of bytes we want to copy this time */
>> +		tocopy = min( 3 - bcd2k->midi_cmd_offset, length - (buf_offset - 1));
>> +		
>> +		if (tocopy > 0) {
>
> tocopy is unsigned char, so this check is always true, and the copy
> routine can overflow in case bcd2k->midi_cmd_offset < 3.

I don't understand your point here. It could be zero. But I changed it
to a condition that checks if both offsets are within the length of the
two involved buffers.

> Please, no dead code. Remove those lines entirely if you don't need them.

Ah okay, I planned to reactive them with the audio part. But I removed
them for now.

As far as I understood, I should repost the new patch as [PATCH v2]. I
will check this evening if the device still works and send it to the
list afterwards.

Thank you!
Mario

  reply	other threads:[~2014-02-05 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01 19:54 [PATCH] MIDI driver for Behringer BCD2000 USB device Mario Kicherer
2014-02-05 10:54 ` Daniel Mack
2014-02-05 15:33   ` Mario Kicherer [this message]
2014-02-05 15:49     ` Daniel Mack
  -- strict thread matches above, loose matches on Subject: below --
2014-02-20 12:31 Mario Kicherer
2014-02-20 12:44 ` Daniel Mack

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=52F259D0.9070705@kicherer.org \
    --to=dev@kicherer.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=daniel@zonque.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