From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH v3] amixer: skip showing asoc tlv byte controls
Date: Thu, 28 Jan 2016 13:54:24 +0530 [thread overview]
Message-ID: <20160128082424.GI11130@localhost> (raw)
In-Reply-To: <s5hegd2maa2.wl-tiwai@suse.de>
On Thu, Jan 28, 2016 at 08:29:57AM +0100, Takashi Iwai wrote:
> On Thu, 28 Jan 2016 08:26:06 +0100,
> Vinod Koul wrote:
> >
> > ASoC TLV Byte controls are very large size controls so we should add new
> > options for these. So skip dumping contents for these.
> >
> > $amixer -c0 cget numid=16
> > numid=16,iface=MIXER,name='mdl params'
> > ; type=BYTES,access=-----RW-,values=30336
> > : ASoC TLV Byte control, skipping bytes dump
>
> Use semicolon instead.
Sure, I tried to use the existing style, what is the interpretation of
these?
--
~Vinod
prev parent reply other threads:[~2016-01-28 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 7:26 [PATCH v3] amixer: skip showing asoc tlv byte controls Vinod Koul
2016-01-28 7:29 ` Takashi Iwai
2016-01-28 8:24 ` Vinod Koul [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=20160128082424.GI11130@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).