From: Takashi Iwai <tiwai@suse.de>
To: Minjie Du <duminjie@vivo.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
alsa-devel@alsa-project.org (moderated list:SOUND),
linux-kernel@vger.kernel.org (open list),
opensource.kernel@vivo.com
Subject: Re: [PATCH v1] sound: seq: check struct system assignment problem
Date: Wed, 05 Jul 2023 10:55:37 +0200 [thread overview]
Message-ID: <87a5waohyu.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230705085022.13078-1-duminjie@vivo.com>
On Wed, 05 Jul 2023 10:50:22 +0200,
Minjie Du wrote:
>
> make data->system.parm1 avoid double assignment.
> but note writes "RT message with two parameters to UMP"
> is one of assignment is for system.parm2?
Yes, that should be rather parm2.
Could you resubmit with that typo fix instead?
Thanks!
Takashi
> I'm not sure, Could you help check it out?
> Thank you!
>
>
> Signed-off-by: Minjie Du <duminjie@vivo.com>
> ---
> sound/core/seq/seq_ump_convert.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/sound/core/seq/seq_ump_convert.c b/sound/core/seq/seq_ump_convert.c
> index eb1d86ff6..60e637149 100644
> --- a/sound/core/seq/seq_ump_convert.c
> +++ b/sound/core/seq/seq_ump_convert.c
> @@ -713,7 +713,6 @@ static int system_2p_ev_to_ump_midi1(const struct snd_seq_event *event,
> unsigned char status)
> {
> data->system.status = status;
> - data->system.parm1 = (event->data.control.value >> 7) & 0x7f;
> data->system.parm1 = event->data.control.value & 0x7f;
> return 1;
> }
> --
> 2.39.0
>
prev parent reply other threads:[~2023-07-05 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 8:50 [PATCH v1] sound: seq: check struct system assignment problem Minjie Du
2023-07-05 8:55 ` 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=87a5waohyu.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=duminjie@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=perex@perex.cz \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.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