All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Kalderon <mkalderon@marvell.com>
To: Doug Ledford <dledford@redhat.com>, "jgg@ziepe.ca" <jgg@ziepe.ca>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: RE: [EXT] Re: [PATCH rdma-rc] RDMA/qedr: Fix the hca_type and hca_rev returned in device attributes
Date: Mon, 29 Jul 2019 18:57:24 +0000	[thread overview]
Message-ID: <MN2PR18MB3182453FD6E5E2C8D5F3C835A1DD0@MN2PR18MB3182.namprd18.prod.outlook.com> (raw)
In-Reply-To: <e6a930259f457a6d4dabfef0265545cff02ee427.camel@redhat.com>

> From: Doug Ledford <dledford@redhat.com>
> Sent: Monday, July 29, 2019 8:24 PM
> 
> External Email
> 
> ----------------------------------------------------------------------
> On Sun, 2019-07-28 at 14:13 +0300, Michal Kalderon wrote:
> > There was a place holder for hca_type and vendor was returned in
> > hca_rev. Fix the hca_rev to return the hw revision and fix the
> > hca_type to return an informative string representing the hca.
> >
> > Signed-off-by: Michal Kalderon <michal.kalderon@marvell.com>
> 
> This one was really kind of borderline for belonging in rc.  In the end, I took it
> there because you requested it in your submission, but I think it could have
> easily waited in for-next too.  Anyway, thanks, applied.

Thanks. 

> 
> --
> Doug Ledford <dledford@redhat.com>
>     GPG KeyID: B826A3330E572FDD
>     Fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

      reply	other threads:[~2019-07-29 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28 11:13 [PATCH rdma-rc] RDMA/qedr: Fix the hca_type and hca_rev returned in device attributes Michal Kalderon
2019-07-29 17:24 ` Doug Ledford
2019-07-29 18:57   ` Michal Kalderon [this message]

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=MN2PR18MB3182453FD6E5E2C8D5F3C835A1DD0@MN2PR18MB3182.namprd18.prod.outlook.com \
    --to=mkalderon@marvell.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --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 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.