From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Max Kellermann <max.kellermann@gmail.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 1/2] [media] xc4000: Delete two error messages for a failed memory allocation in xc4000_fwupload()
Date: Sat, 9 Sep 2017 21:13:40 +0200 [thread overview]
Message-ID: <0ad4caf5-a0fd-2852-5d01-9c9e45a9e480@users.sourceforge.net> (raw)
In-Reply-To: <61016489-eb01-2977-b094-343aa70686b0@users.sourceforge.net>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Sat, 9 Sep 2017 20:46:35 +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/xc4000.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/media/tuners/xc4000.c b/drivers/media/tuners/xc4000.c
index e30948e4ff87..bbf386127fc4 100644
--- a/drivers/media/tuners/xc4000.c
+++ b/drivers/media/tuners/xc4000.c
@@ -779,4 +779,3 @@ static int xc4000_fwupload(struct dvb_frontend *fe)
- printk(KERN_ERR "Not enough memory to load firmware file.\n");
rc = -ENOMEM;
goto done;
}
@@ -826,4 +825,3 @@ static int xc4000_fwupload(struct dvb_frontend *fe)
- printk(KERN_ERR "Not enough memory to load firmware file.\n");
rc = -ENOMEM;
goto done;
}
--
2.14.1
next prev parent reply other threads:[~2017-09-09 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 19:12 [PATCH 0/2] [media] xc4000: Adjustments for xc4000_fwupload() SF Markus Elfring
2017-09-09 19:13 ` SF Markus Elfring [this message]
2017-09-09 19:14 ` [PATCH 2/2] [media] xc4000: Adjust two null pointer checks in xc4000_fwupload() 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=0ad4caf5-a0fd-2852-5d01-9c9e45a9e480@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=max.kellermann@gmail.com \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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
Powered by JetHome