From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: soc-cache: Return -ENOSYS instead of -EINVAL
Date: Sat, 26 Mar 2011 17:41:00 +0000 [thread overview]
Message-ID: <20110326174059.GG3535@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1300790929-26302-1-git-send-email-dp@opensource.wolfsonmicro.com>
On Tue, Mar 22, 2011 at 10:48:49AM +0000, Dimitris Papastamos wrote:
> These functions fail with -EINVAL if the corresponding callbacks
> are not implemented. Change them to return -ENOSYS as it is more
> appropriate for unimplemented callbacks.
>
> Signed-off-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Applied, thanks.
prev parent reply other threads:[~2011-03-26 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 10:48 [PATCH] ASoC: soc-cache: Return -ENOSYS instead of -EINVAL Dimitris Papastamos
2011-03-26 17:41 ` Mark Brown [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=20110326174059.GG3535@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=patches@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).