From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-media@vger.kernel.org, Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 1/3] [media] xc2028: Delete two error messages for a failed memory allocation in load_all_firmwares()
Date: Sat, 9 Sep 2017 22:31:13 +0200 [thread overview]
Message-ID: <8c68a1b2-5e6b-ab26-290b-3f9ab46f7a42@users.sourceforge.net> (raw)
In-Reply-To: <c2317603-f640-b0a6-ab86-7fda8040b6ba@users.sourceforge.net>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Sat, 9 Sep 2017 21:30:11 +0200
Omit extra messages for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
drivers/media/tuners/tuner-xc2028.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/media/tuners/tuner-xc2028.c b/drivers/media/tuners/tuner-xc2028.c
index b5b62b08159e..7353f25f9e7d 100644
--- a/drivers/media/tuners/tuner-xc2028.c
+++ b/drivers/media/tuners/tuner-xc2028.c
@@ -339,4 +339,3 @@ static int load_all_firmwares(struct dvb_frontend *fe,
- tuner_err("Not enough memory to load firmware file.\n");
rc = -ENOMEM;
goto err;
}
@@ -389,4 +388,3 @@ static int load_all_firmwares(struct dvb_frontend *fe,
- tuner_err("Not enough memory to load firmware file.\n");
rc = -ENOMEM;
goto err;
}
--
2.14.1
next prev parent reply other threads:[~2017-09-09 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 20:30 [PATCH 0/3] [media] xc2028: Adjustments for two function implementations SF Markus Elfring
2017-09-09 20:31 ` SF Markus Elfring [this message]
2017-09-09 20:32 ` [PATCH 2/3] [media] xc2028: Adjust two null pointer checks in load_all_firmwares() SF Markus Elfring
2017-09-09 20:33 ` [PATCH 3/3] [media] xc2028: Use common error handling code in load_firmware() SF Markus Elfring
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=8c68a1b2-5e6b-ab26-290b-3f9ab46f7a42@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.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
all inboxes | Powered by JetHome®