From: javier@osg.samsung.com (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] media: s5p-mfc remove unnecessary error messages
Date: Thu, 14 Jul 2016 08:46:34 -0400 [thread overview]
Message-ID: <c38dc1b5-e2f7-4486-a0fc-a8f690d28fe6@osg.samsung.com> (raw)
In-Reply-To: <1468370038-5364-1-git-send-email-shuahkh@osg.samsung.com>
Hello Shuah,
On 07/12/2016 08:33 PM, Shuah Khan wrote:
> Removing unnecessary error messages as appropriate error code is returned.
>
> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
> ---
> drivers/media/platform/s5p-mfc/s5p_mfc.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc.c b/drivers/media/platform/s5p-mfc/s5p_mfc.c
> index b6fde20..906f80c 100644
> --- a/drivers/media/platform/s5p-mfc/s5p_mfc.c
> +++ b/drivers/media/platform/s5p-mfc/s5p_mfc.c
> @@ -759,7 +759,6 @@ static int s5p_mfc_open(struct file *file)
> /* Allocate memory for context */
> ctx = kzalloc(sizeof(*ctx), GFP_KERNEL);
> if (!ctx) {
> - mfc_err("Not enough memory\n");
I agree to remove this since in case of a OOM, the core already does a
stack dump and prints an error message so there's no need to it here.
> ret = -ENOMEM;
> goto err_alloc;
> }
> @@ -776,7 +775,6 @@ static int s5p_mfc_open(struct file *file)
> while (dev->ctx[ctx->num]) {
> ctx->num++;
> if (ctx->num >= MFC_NUM_CONTEXTS) {
> - mfc_err("Too many open contexts\n");
But I think this error message shouldn't be removed since explains why
the open failed, even when an error code is returned.
> ret = -EBUSY;
> goto err_no_ctx;
> }
>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2016-07-14 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 0:33 [PATCH] media: s5p-mfc remove unnecessary error messages Shuah Khan
2016-07-14 12:46 ` Javier Martinez Canillas [this message]
2016-07-14 13:35 ` Shuah Khan
2016-07-14 13:36 ` Javier Martinez Canillas
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=c38dc1b5-e2f7-4486-a0fc-a8f690d28fe6@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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