From: Takashi Iwai <tiwai@suse.de>
To: Julian Anastasov <ja@ssi.bg>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb-audio: fix combine_word problem
Date: Sat, 07 Nov 2009 10:22:45 +0100 [thread overview]
Message-ID: <s5h8weiy9i2.wl%tiwai@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0911062329380.7491@u.domain.uli>
At Fri, 6 Nov 2009 23:44:53 +0200 (EET),
Julian Anastasov wrote:
>
>
> Fix combine_word problem where first octet is not
> read properly. The only affected place seems to be the
> INPUT_TERMINAL type. Before now, sound controls can be created
> with the output terminal's name which is a fallback mechanism
> used only for unknown input terminal types. For example,
> Line can wrongly appear as Speaker. After the change it
> should appear as Line.
Wow, this is really an old bug. I wonder no one noticed it, so far...
> The side effect of this change can be that users
> can expect the wrong control name in their scripts or
> programs while now we return the correct one.
Yes, but it's a right "fix", so let it be.
> Probably, these defines should use get_unaligned_le16 and
> friends.
Sounds like a good idea. But 24bit version is still missing :)
> Signed-off-by: Julian Anastasov <ja@ssi.bg>
Applied now, and added Cc to stable kernel.
Thanks!
Takashi
> ---
>
> diff -urp v2.6.31/linux/sound/usb/usbaudio.h linux/sound/usb/usbaudio.h
> --- v2.6.31/linux/sound/usb/usbaudio.h 2009-06-13 10:53:59.000000000 +0300
> +++ linux/sound/usb/usbaudio.h 2009-11-06 22:38:00.000000000 +0200
> @@ -210,7 +210,7 @@ struct snd_usb_midi_endpoint_info {
> /*
> */
>
> -#define combine_word(s) ((*s) | ((unsigned int)(s)[1] << 8))
> +#define combine_word(s) ((*(s)) | ((unsigned int)(s)[1] << 8))
> #define combine_triple(s) (combine_word(s) | ((unsigned int)(s)[2] << 16))
> #define combine_quad(s) (combine_triple(s) | ((unsigned int)(s)[3] << 24))
>
>
prev parent reply other threads:[~2009-11-07 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 21:44 Julian Anastasov
2009-11-07 9:22 ` Takashi Iwai [this message]
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=s5h8weiy9i2.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=ja@ssi.bg \
--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®