mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/
synced 2026-10-14 05:55:17 +00:00
No description
- C 96.9%
- Assembly 0.9%
- Rust 0.6%
- Shell 0.6%
- Python 0.5%
- Other 0.3%
3722e4ecefHi Mark
Indicating error message when failed case is very useful for debuging.
In many case, it uses below style.
int function(...)
{
...
return ret;
}
int caller(...)
{
...
ret = function(...);
if (ret < 0)
dev_err(...)
...
}
This is not so bad, but in this style *each caller* needs to indicate
duplicate same error message, and some caller is forgetting to do it.
And caller can't indicate detail function() error information.
I know many people have many opinion, but if function() indicates error
message, we can get same and detail information without forgot, and it is better.
This patch-set tidyup to do it.
int function(...)
{
...
if (ret < 0)
dev_err(...)
return ret;
}
int caller(...)
{
...
ret = function(...);
...
}
Kuninori Morimoto (14):
ASoC: soc-pcm: indicate error message at soc_pcm_open()
ASoC: soc-pcm: indicate error message at soc_pcm_hw_params()
ASoC: soc-pcm: indicate error message at soc_pcm_prepare()
ASoC: soc-pcm: indicate error message at dpcm_path_get()
ASoC: soc-pcm: indicate error message at dpcm_be_dai_trigger()
ASoC: soc-pcm: indicate error message at dpcm_apply_symmetry()
ASoC: soc-pcm: indicate error message at dpcm_run_update_startup/shutdown()
ASoC: soc-pcm: indicate error message at dpcm_fe/be_dai_startup()
ASoC: soc-pcm: indicate error message at dpcm_fe/be_dai_hw_params()
ASoC: soc-pcm: indicate error message at dpcm_fe/be_dai_prepare()
ASoC: soc-pcm: don't indicate error message for soc_pcm_hw_free()
ASoC: soc-pcm: don't indicate error message for dpcm_be_dai_hw_free()
ASoC: don't indicate error message for snd_soc_[pcm_]dai_xxx()
ASoC: don't indicate error message for snd_soc_[pcm_]component_xxx()
include/sound/soc-dpcm.h | 2 +-
sound/soc/soc-compress.c | 9 +-
sound/soc/soc-core.c | 22 +----
sound/soc/soc-dapm.c | 24 ++---
sound/soc/soc-pcm.c | 197 +++++++++++++++++++--------------------
5 files changed, 108 insertions(+), 146 deletions(-)
--
2.25.1
|
History
|
|
|---|---|---|
| arch | ||
| block | ||
| certs | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| fs | ||
| include | ||
| init | ||
| ipc | ||
| kernel | ||
| lib | ||
| LICENSES | ||
| mm | ||
| net | ||
| samples | ||
| scripts | ||
| security | ||
| sound | ||
| tools | ||
| usr | ||
| virt | ||
| .clang-format | ||
| .cocciconfig | ||
| .get_maintainer.ignore | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| COPYING | ||
| CREDITS | ||
| Kbuild | ||
| Kconfig | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
Linux kernel
============
There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.
In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``. The formatted documentation can also be read online at:
https://www.kernel.org/doc/html/latest/
There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.
Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.