From: Leon Romanovsky <leon@kernel.org>
To: Igor Stoppa <igor.stoppa@gmail.com>
Cc: Doug Ledford <dledford@redhat.com>,
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 20:31:54 +0300 [thread overview]
Message-ID: <20180907173154.GT3142@mtr-leonro.mtl.com> (raw)
In-Reply-To: <e7fac148-2347-1303-7725-41b7858a02e4@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Fri, Sep 07, 2018 at 06:25:03PM +0300, Igor Stoppa wrote:
> 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
You didn't do anything wrong, I was curious because my gmail already
filtered some linux-rdma mails to wrong folder and I wasn't sure if
it is the case again.
Thanks
>
> --
> igor
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2018-09-07 17:31 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
2018-09-07 17:31 ` Leon Romanovsky [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=20180907173154.GT3142@mtr-leonro.mtl.com \
--to=leon@kernel.org \
--cc=chien.tin.tung@intel.com \
--cc=dledford@redhat.com \
--cc=faisal.latif@intel.com \
--cc=igor.stoppa@gmail.com \
--cc=igor.stoppa@huawei.com \
--cc=jgg@ziepe.ca \
--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