All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: fuweix.tang@intel.com
Cc: liam.r.girdwood@linux.intel.com, mengdong.lin@intel.com,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH v2] topology: Fix issue in parsing routes when generating topology binary
Date: Fri, 05 May 2017 10:09:37 +0200	[thread overview]
Message-ID: <s5hshkjn2ri.wl-tiwai@suse.de> (raw)
In-Reply-To: <1493971040-15628-1-git-send-email-fuweix.tang@intel.com>

On Fri, 05 May 2017 09:57:20 +0200,
fuweix.tang@intel.com wrote:
> 
> From: Fuwei Tang <fuweix.tang@intel.com>
> 
> We missed parsing the index value, which is used as a use case indicator, when
> processing the route objects.
> 
> This patch fixes the bug.
> 
> Signed-off-by: Fuwei Tang <fuweix.tang@intel.com>
> Tested-by: Subhransu S. Prusty <subhransu.s.prusty@intel.com>

Applied, thanks.


Takashi

      reply	other threads:[~2017-05-05  8:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05  7:57 [PATCH v2] topology: Fix issue in parsing routes when generating topology binary fuweix.tang
2017-05-05  8:09 ` 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=s5hshkjn2ri.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=fuweix.tang@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=mengdong.lin@intel.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 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.