linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Gal Pressman <galpress@amazon.com>
Cc: Doug Ledford <dledford@redhat.com>,
	linux-rdma@vger.kernel.org,
	Daniel Kranzdorf <dkkranzd@amazon.com>,
	Firas JahJah <firasj@amazon.com>
Subject: Re: [PATCH for-next 1/4] RDMA/efa: Fix incorrect error print
Date: Mon, 16 Sep 2019 14:37:00 -0300	[thread overview]
Message-ID: <20190916173700.GA6516@ziepe.ca> (raw)
In-Reply-To: <20190910134301.4194-2-galpress@amazon.com>

On Tue, Sep 10, 2019 at 02:42:58PM +0100, Gal Pressman wrote:
> The error print should indicate that it failed to get the queue
> attributes, not network attributes.
> 
> Reviewed-by: Daniel Kranzdorf <dkkranzd@amazon.com>
> Reviewed-by: Firas JahJah <firasj@amazon.com>
> Signed-off-by: Gal Pressman <galpress@amazon.com>
>  drivers/infiniband/hw/efa/efa_com_cmd.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Safe enough to apply to for-next, thanks

Jason

  reply	other threads:[~2019-09-16 17:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10 13:42 [PATCH for-next 0/4] EFA RDMA read support Gal Pressman
2019-09-10 13:42 ` [PATCH for-next 1/4] RDMA/efa: Fix incorrect error print Gal Pressman
2019-09-16 17:37   ` Jason Gunthorpe [this message]
2019-09-10 13:42 ` [PATCH for-next 2/4] RDMA/efa: Store network attributes in device attributes Gal Pressman
2019-09-10 13:43 ` [PATCH for-next 3/4] RDMA/efa: Support remote read access in MR registration Gal Pressman
2019-09-10 13:43 ` [PATCH for-next 4/4] RDMA/efa: Expose RDMA read related attributes Gal Pressman
2019-10-20  7:03 ` [PATCH for-next 0/4] EFA RDMA read support Gal Pressman
2019-10-21 17:31   ` Jason Gunthorpe
2019-10-23  9:55     ` Gal Pressman
2019-10-23 14:35       ` Jason Gunthorpe

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=20190916173700.GA6516@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=dkkranzd@amazon.com \
    --cc=dledford@redhat.com \
    --cc=firasj@amazon.com \
    --cc=galpress@amazon.com \
    --cc=linux-rdma@vger.kernel.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 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).