From: dledford@redhat.com (Doug Ledford)
Subject: [PATCH] mlx5: fix mlx5_get_vector_affinity to start from completion vector 0
Date: Mon, 05 Feb 2018 10:23:32 -0500 [thread overview]
Message-ID: <1517844212.3936.64.camel@redhat.com> (raw)
In-Reply-To: <64670132-9662-9bbe-9979-fd02260a7fb3@grimberg.me>
On Mon, 2018-02-05@16:28 +0200, Sagi Grimberg wrote:
> Sorry, now my .gitaliases updated with Jason's correct email.
Jason prefers jgg at ziepe.ca for his upstream work, so might need to
update again ;-)
--
Doug Ledford <dledford at redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20180205/b3e1d858/attachment.sig>
next prev parent reply other threads:[~2018-02-05 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 14:24 [PATCH] mlx5: fix mlx5_get_vector_affinity to start from completion vector 0 Sagi Grimberg
2018-02-05 14:28 ` Sagi Grimberg
2018-02-05 15:23 ` Doug Ledford [this message]
2018-02-05 15:28 ` Sagi Grimberg
2018-02-05 15:57 ` Doug Ledford
2018-02-05 17:16 ` Logan 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=1517844212.3936.64.camel@redhat.com \
--to=dledford@redhat.com \
/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