From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Leon Romanovsky' <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH rdma-next 07/17] IB/cxgb3: Remove debug prints after allocation failure
Date: Thu, 3 Nov 2016 09:32:10 -0500 [thread overview]
Message-ID: <0ba301d235df$10155ba0$304012e0$@opengridcomputing.com> (raw)
In-Reply-To: <1478149353-12125-8-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>
> The prints after [k|v][m|z|c]alloc() functions are not needed,
> because in case of failure, allocator will print their internal
> error prints anyway.
>
> Signed-off-by: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Acked-by: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-11-03 14:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 5:02 [PATCH rdma-next 00/17] Remove debug prints after allocation failure Leon Romanovsky
[not found] ` <1478149353-12125-1-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-11-03 5:02 ` [PATCH rdma-next 01/17] IB/mad: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 02/17] IB/core: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 03/17] IB/core: Release allocated memory in cache setup failure Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 04/17] IB/mlx4: Remove debug prints after allocation failure Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 05/17] IB/mlx5: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 06/17] IB/hfi1: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 07/17] IB/cxgb3: " Leon Romanovsky
[not found] ` <1478149353-12125-8-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-11-03 14:32 ` Steve Wise [this message]
2016-11-03 5:02 ` [PATCH rdma-next 08/17] IB/cxgb4: " Leon Romanovsky
[not found] ` <1478149353-12125-9-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-11-03 14:32 ` Steve Wise
2016-11-03 5:02 ` [PATCH rdma-next 09/17] IB/i40iw: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 10/17] IB/qib: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 11/17] IB/nes: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 12/17] IB/mthca: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 13/17] IB/usninc: Remove and fix " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 14/17] IB/ocrdma: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 15/17] IB/rxe: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 16/17] IB/isert: " Leon Romanovsky
2016-11-03 5:02 ` [PATCH rdma-next 17/17] IB/ipoib: " Leon Romanovsky
2016-12-03 18:21 ` [PATCH rdma-next 00/17] Remove " Doug Ledford
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='0ba301d235df$10155ba0$304012e0$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.