From: SF Markus Elfring <elfring@users.sourceforge.net>
To: netdev@vger.kernel.org, Andy Gospodarek <andy@greyhouse.net>,
Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH] bonding: Delete an error message for a failed memory allocation in bond_update_slave_arr()
Date: Mon, 1 Jan 2018 17:07:20 +0100 [thread overview]
Message-ID: <6cdc726b-82bc-85b6-393b-0e2002c19341@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Mon, 1 Jan 2018 17:00:04 +0100
Omit an extra message 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/net/bonding/bond_main.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
index c669554d70bb..a96e0c9cc4bf 100644
--- a/drivers/net/bonding/bond_main.c
+++ b/drivers/net/bonding/bond_main.c
@@ -3910,7 +3910,6 @@ int bond_update_slave_arr(struct bonding *bond, struct slave *skipslave)
GFP_KERNEL);
if (!new_arr) {
ret = -ENOMEM;
- pr_err("Failed to build slave-array.\n");
goto out;
}
if (BOND_MODE(bond) == BOND_MODE_8023AD) {
--
2.15.1
next reply other threads:[~2018-01-01 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 16:07 SF Markus Elfring [this message]
2018-01-03 7:00 ` [PATCH] bonding: Delete an error message for a failed memory allocation in bond_update_slave_arr() Mahesh Bandewar (महेश बंडेवार)
2018-01-03 8:45 ` SF Markus Elfring
2018-01-03 19:28 ` Mahesh Bandewar (महेश बंडेवार)
2018-01-03 21:58 ` Eric Dumazet
2018-01-04 8:19 ` bonding: Completion of error handling around bond_update_slave_arr() SF Markus Elfring
2018-01-04 18:52 ` Mahesh Bandewar (महेश बंडेवार)
2018-01-04 21:41 ` 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=6cdc726b-82bc-85b6-393b-0e2002c19341@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=andy@greyhouse.net \
--cc=j.vosburgh@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.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).