All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	RDMA mailing list
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH rdma-next] RDMA/mlx5; Remove redundant allocation warning print
Date: Fri, 19 Jan 2018 12:58:40 +0200	[thread overview]
Message-ID: <20180119105840.GA1393@mtr-leonro.local> (raw)
In-Reply-To: <20180118200211.GA17561@yuvallap>

[-- Attachment #1: Type: text/plain, Size: 2432 bytes --]

On Thu, Jan 18, 2018 at 10:02:12PM +0200, Yuval Shaia wrote:
> On Thu, Jan 18, 2018 at 02:34:24PM +0200, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> >
> > The kmalloc() failure to allocate memory generates enough information
> > and doesn't need to be accompanied by another driver print.
> >
> > Fixes: d69a24e03659 ("IB/mlx5: Move IB event processing onto a workqueue")
>
> Didn't found it in:
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/leon/linux-rdma/
> branch rdma-next and didn't find it.
> Where should i look?

In official place:
https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/?h=for-next&id=d69a24e036596877ce08c25ab8e63a202412fd9e

>
> > Signed-off-by: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> > ---
> >  drivers/infiniband/hw/mlx5/main.c | 20 +++++++++-----------
> >  1 file changed, 9 insertions(+), 11 deletions(-)
> >
> > diff --git a/drivers/infiniband/hw/mlx5/main.c b/drivers/infiniband/hw/mlx5/main.c
> > index f282e281eff2..91688352b5d7 100644
> > --- a/drivers/infiniband/hw/mlx5/main.c
> > +++ b/drivers/infiniband/hw/mlx5/main.c
> > @@ -3345,19 +3345,17 @@ static void mlx5_ib_event(struct mlx5_core_dev *dev, void *context,
> >  	struct mlx5_ib_event_work *work;
> >
> >  	work = kmalloc(sizeof(*work), GFP_ATOMIC);
> > -	if (work) {
> > -		INIT_WORK(&work->work, mlx5_ib_handle_event);
> > -		work->dev = dev;
> > -		work->param = param;
> > -		work->context = context;
> > -		work->event = event;
> > -
> > -		queue_work(mlx5_ib_event_wq, &work->work);
> > +	if (!work)
> >  		return;
> > -	}
> >
> > -	dev_warn(&dev->pdev->dev, "%s: mlx5_dev_event: %d, with param: %lu dropped, couldn't allocate memory.\n",
> > -		 __func__, event, param);
> > +	INIT_WORK(&work->work, mlx5_ib_handle_event);
> > +	work->dev = dev;
> > +	work->param = param;
> > +	work->context = context;
> > +	work->event = event;
> > +
> > +	queue_work(mlx5_ib_event_wq, &work->work);
> > +	return;
>
> We don't really need this last "return", right?

Right, I'll remove it now.

Thanks

>
> >  }
> >
> >  static int set_has_smi_cap(struct mlx5_ib_dev *dev)
> > --
> > 2.15.1
> >
> > --
> > 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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-01-19 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 12:34 [PATCH rdma-next] RDMA/mlx5; Remove redundant allocation warning print Leon Romanovsky
     [not found] ` <20180118123424.21062-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-18 20:02   ` Yuval Shaia
2018-01-19 10:58     ` Leon Romanovsky [this message]
     [not found]       ` <20180119105840.GA1393-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-19 18:54         ` Yuval Shaia
2018-01-21 13:41           ` Leon Romanovsky

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=20180119105840.GA1393@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@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.