From: Mark Brown <broonie@kernel.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
tiwai@suse.com, lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: tas2562: Return invalid for when bitwidth is invalid
Date: Tue, 18 Feb 2020 18:48:32 +0000 [thread overview]
Message-ID: <20200218184832.GL4232@sirena.org.uk> (raw)
In-Reply-To: <20200218174706.27309-1-dmurphy@ti.com>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
On Tue, Feb 18, 2020 at 11:47:06AM -0600, Dan Murphy wrote:
> If the bitwidth passed in to the set_bitwidth function is not supported
> then return an error.
>
> Fixes: 29b74236bd57 ("ASoC: tas2562: Introduce the TAS2562 amplifier")
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
> scripts/conmakehash | Bin 0 -> 13120 bytes
> scripts/sortextable | Bin 0 -> 18040 bytes
> sound/soc/codecs/tas2562.c | 3 ++-
> 3 files changed, 2 insertions(+), 1 deletion(-)
> create mode 100755 scripts/conmakehash
> create mode 100755 scripts/sortextable
>
> diff --git a/scripts/conmakehash b/scripts/conmakehash
> new file mode 100755
> index 0000000000000000000000000000000000000000..17eec37019b8ae45f42f3c82046d1a55a6f69cb3
> GIT binary patch
> literal 13120
> zcmeHOeQ;D&mcN}25CU`u1i`Q23C#=v(j@XB0Wx-n4!le?@~!SFHl6fK(rc$X+x=RD
This is... fun? I'm guessing it's not intentional, it's certainly a
little difficult to review. :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-18 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 17:47 [PATCH] ASoC: tas2562: Return invalid for when bitwidth is invalid Dan Murphy
2020-02-18 18:48 ` Mark Brown [this message]
2020-02-18 18:52 ` Dan Murphy
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=20200218184832.GL4232@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=dmurphy@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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