From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 0/2] ASoC: omap: Fix enum ctl accesses
Date: Mon, 29 Feb 2016 22:16:32 +0200 [thread overview]
Message-ID: <56D4A720.3070504@bitmer.com> (raw)
In-Reply-To: <1456763182-2986-1-git-send-email-tiwai@suse.de>
On 02/29/2016 06:26 PM, Takashi Iwai wrote:
> Hi,
>
> here is a patchset to correct the wrong type accesses in omap drivers
> for enum ctls. I didn't put Cc to stable for them, supposing these
> are only for 32bit systems. If not, feel free to put Cc to stable.
>
>
> thanks,
>
> Takashi
>
> ===
>
> Takashi Iwai (2):
> ASoC: omap: n810: Fix enum ctl accesses in a wrong type
> ASoC: omap: rx51: Fix enum ctl accesses in a wrong type
>
> sound/soc/omap/n810.c | 18 +++++++++---------
> sound/soc/omap/rx51.c | 18 +++++++++---------
> 2 files changed, 18 insertions(+), 18 deletions(-)
>
No need to Cc stable with these. Both are 32-bit LE ARMs and thus
incorrect use of long instead of unsigned int haven't caused problems
due only positive integers value used here.
--
Jarkko
prev parent reply other threads:[~2016-02-29 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 16:26 [PATCH 0/2] ASoC: omap: Fix enum ctl accesses Takashi Iwai
2016-02-29 16:26 ` [PATCH 1/2] ASoC: omap: n810: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-03-01 3:24 ` Applied "ASoC: omap: n810: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-02-29 16:26 ` [PATCH 2/2] ASoC: omap: rx51: Fix enum ctl accesses in a wrong type Takashi Iwai
2016-02-29 19:56 ` Jarkko Nikula
2016-03-01 3:23 ` Applied "ASoC: omap: rx51: Fix enum ctl accesses in a wrong type" to the asoc tree Mark Brown
2016-02-29 20:16 ` Jarkko Nikula [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=56D4A720.3070504@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=peter.ujfalusi@ti.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.