[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c849843-549f-419e-2326-1fcb7bcdc2e2@users.sourceforge.net>
Date: Mon, 22 May 2017 21:46:21 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
linux-sctp@...r.kernel.org, netdev@...r.kernel.org
Cc: "David S. Miller" <davem@...emloft.net>,
Neil Horman <nhorman@...driver.com>,
Vlad Yasevich <vyasevich@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 2/5] sctp: Delete an error message for a failed memory
allocation in sctp_init()
>> +++ b/net/sctp/protocol.c
>> @@ -1447,5 +1447,4 @@ static __init int sctp_init(void)
>> if (!sctp_ep_hashtable) {
>> - pr_err("Failed endpoint_hash alloc\n");
>
> Okay but then why not also delete the one a few lines below this one:
> if (!sctp_port_hashtable) {
> pr_err("Failed bind hash alloc\n");
> status = -ENOMEM;
> goto err_bhash_alloc;
> }
> Seems the same pattern to me.
>
>> status = -ENOMEM;
>> goto err_ehash_alloc;
>> }
How do you think about to remove the other error message in another
update step if a consensus would be achieved in such a direction
for this software module?
Regards,
Markus
Powered by blists - more mailing lists