public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Igor Stoppa <igor.stoppa@gmail.com>
To: Doug Ledford <dledford@redhat.com>, Leon Romanovsky <leon@kernel.org>
Cc: Faisal Latif <faisal.latif@intel.com>,
	Igor Stoppa <igor.stoppa@huawei.com>,
	Chien Tung <chien.tin.tung@intel.com>,
	Roland Dreier <rolandd@cisco.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] infiniband: nes: add unlikely() to assert()
Date: Fri, 7 Sep 2018 18:25:03 +0300	[thread overview]
Message-ID: <e7fac148-2347-1303-7725-41b7858a02e4@gmail.com> (raw)
In-Reply-To: <811a6feca9fdea2db59ac392a4711cd897f46cc7.camel@redhat.com>

On 07/09/18 18:13, Doug Ledford wrote:

> This patch was part of a larger series on lkml.  In that context, I
> acked it so that the series could be applied by whomever took it (it
> didn't belong on rdma-list as a series since only one patch out of some
> large number touched rdma files).  Now it is being resent as not part of
> a series, but my ack was preserved.

Yes, apologies for the confusion (and maybe wrong process?).
The patchset as a whole didn't seem to gain traction, so I decided to 
fallback to the more tedious process of submitting them individually.

Since the specific patch was not altered, I assumed the ack was still 
valid - I am sorry if I did it wrongly

--
igor

  reply	other threads:[~2018-09-07 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 19:24 [PATCH] infiniband: nes: add unlikely() to assert() Igor Stoppa
2018-09-05  6:01 ` Leon Romanovsky
2018-09-05 18:54   ` Igor Stoppa
2018-09-07 15:13   ` Doug Ledford
2018-09-07 15:25     ` Igor Stoppa [this message]
2018-09-07 17:31       ` 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=e7fac148-2347-1303-7725-41b7858a02e4@gmail.com \
    --to=igor.stoppa@gmail.com \
    --cc=chien.tin.tung@intel.com \
    --cc=dledford@redhat.com \
    --cc=faisal.latif@intel.com \
    --cc=igor.stoppa@huawei.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rolandd@cisco.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