All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Max Gurtovoy <maxg@mellanox.com>
Cc: <sagi@grimberg.me>, <linux-rdma@vger.kernel.org>,
	<dledford@redhat.com>, <leonro@mellanox.com>, <oren@mellanox.com>
Subject: Re: [PATCH 2/2] IB/isert: remove duplicated error prints
Date: Tue, 18 Aug 2020 15:41:53 -0300	[thread overview]
Message-ID: <20200818184153.GA2064193@nvidia.com> (raw)
In-Reply-To: <20200805121231.166162-2-maxg@mellanox.com>

On Wed, Aug 05, 2020 at 03:12:31PM +0300, Max Gurtovoy wrote:
> The isert_post_recv function prints an error in case of failures, so no
> need for the callers to add another print.
> 
> Signed-off-by: Max Gurtovoy <maxg@mellanox.com>
> Acked-by: Sagi Grimberg <sagi@grimberg.me>
> ---
>  drivers/infiniband/ulp/isert/ib_isert.c | 15 +++------------
>  1 file changed, 3 insertions(+), 12 deletions(-)

Applied to for-next

I dropped patch 1/1 about the unlikelys

Jason

  parent reply	other threads:[~2020-08-18 18:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 12:12 [PATCH 1/2] IB/isert: use unlikely macro in the fast path Max Gurtovoy
2020-08-05 12:12 ` [PATCH 2/2] IB/isert: remove duplicated error prints Max Gurtovoy
2020-08-06 20:12   ` Sagi Grimberg
2020-08-18 18:41   ` Jason Gunthorpe [this message]
2020-08-05 13:16 ` [PATCH 1/2] IB/isert: use unlikely macro in the fast path Leon Romanovsky
2020-08-05 15:14   ` Max Gurtovoy
2020-08-05 16:06     ` Leon Romanovsky
2020-08-05 16:28       ` Max Gurtovoy
2020-08-05 16:37         ` Leon Romanovsky
2020-08-06 10:56           ` Max Gurtovoy
2020-08-06 19:51           ` Sagi Grimberg
2020-08-07 16:09             ` Leon Romanovsky
2020-08-07 16:33               ` Sagi Grimberg
2020-08-06 19:43 ` Sagi Grimberg

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=20200818184153.GA2064193@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=maxg@mellanox.com \
    --cc=oren@mellanox.com \
    --cc=sagi@grimberg.me \
    /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.