From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: Skip napi_schedule if ib_poll_cq fails (v2)
Date: Wed, 13 Jul 2016 18:32:52 +0300 [thread overview]
Message-ID: <20160713153252.GG10079@leon.nu> (raw)
In-Reply-To: <1468423316-28246-1-git-send-email-yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
On Wed, Jul 13, 2016 at 08:21:55AM -0700, Yuval Shaia wrote:
> v0 -> v1:
> * Initialize n before use
>
> v1 -> v2
> * Add reviewers
You don't need to resend patches with tags changes only.
Patchworks handles it and adds automatically when Doug
collects them before apply.
And it will be great if you avoid adding cover letter for one patch.
Thanks
>
> [PATCH v2] IB/ipoib: Skip napi_schedule if ib_poll_cq fails
> --
> 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: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-13 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 15:21 Skip napi_schedule if ib_poll_cq fails (v2) Yuval Shaia
[not found] ` <1468423316-28246-1-git-send-email-yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2016-07-13 15:21 ` [PATCH v2] IB/ipoib: Skip napi_schedule if ib_poll_cq fails Yuval Shaia
2016-07-13 15:32 ` Leon Romanovsky [this message]
[not found] ` <20160713153252.GG10079-2ukJVAZIZ/Y@public.gmane.org>
2016-07-13 18:44 ` Skip napi_schedule if ib_poll_cq fails (v2) Yuval Shaia
2016-07-14 5:11 ` 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=20160713153252.GG10079@leon.nu \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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 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).