mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiada Wang <jiada_wang@mentor.com>
To: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
	<tiwai@suse.com>, <kuninori.morimoto.gx@renesas.com>
Cc: <jiada_wang@mentor.com>, <alsa-devel@alsa-project.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH linux-next v2 0/2] misc fix in src.c
Date: Thu, 7 Mar 2019 15:15:52 +0900	[thread overview]
Message-ID: <20190307061554.26486-1-jiada_wang@mentor.com> (raw)

two issues were found due to linux-next commit
7674bec4fc09 ("ASoC: rsnd: update BSDSR/BSDISR handling")
this patch-set address these two issues

---
v2: Update rsnd_of_match table instead of set priv->flags in probe

v1: initial version

Jiada Wang (2):
  ASoC: rsnd: src: Avoid a potential deadlock
  ASoC: rsnd: src: fix compiler warnings

 sound/soc/sh/rcar/core.c |  3 +++
 sound/soc/sh/rcar/rsnd.h |  5 +++++
 sound/soc/sh/rcar/src.c  | 21 +++++++--------------
 3 files changed, 15 insertions(+), 14 deletions(-)

-- 
2.19.2


             reply	other threads:[~2019-03-07  6:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  6:15 Jiada Wang [this message]
2019-03-07  6:15 ` [PATCH linux-next v2 1/2] ASoC: rsnd: src: Avoid a potential deadlock Jiada Wang
2019-03-11 17:23   ` Applied "ASoC: rsnd: src: Avoid a potential deadlock" to the asoc tree Mark Brown
2019-03-12  9:15   ` [PATCH linux-next v2 1/2] ASoC: rsnd: src: Avoid a potential deadlock Geert Uytterhoeven
2019-03-13 11:55     ` Jiada Wang
2019-03-13 18:19       ` Fabrizio Castro
2019-03-19  3:34         ` Jiada Wang
2019-03-07  6:15 ` [PATCH linux-next v2 2/2] ASoC: rsnd: src: fix compiler warnings Jiada Wang
2019-03-07  6:20 ` [PATCH linux-next v2 0/2] misc fix in src.c Kuninori Morimoto

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=20190307061554.26486-1-jiada_wang@mentor.com \
    --to=jiada_wang@mentor.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --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

all inboxes | Powered by JetHome®