From: Doug Ledford <dledford@redhat.com>
To: Colin Ian King <colin.king@canonical.com>,
Leon Romanovsky <leon@kernel.org>
Cc: Moni Shoua <monis@mellanox.com>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
linux-rdma@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IB/rxe: check for allocation failure on elem
Date: Mon, 09 Oct 2017 16:13:11 +0000 [thread overview]
Message-ID: <1507565591.46071.32.camel@redhat.com> (raw)
In-Reply-To: <a43bfb4f-e7c3-f6be-8946-952fb2d4af14@canonical.com>
On Mon, 2017-10-09 at 14:18 +0100, Colin Ian King wrote:
> On 09/10/17 14:16, Doug Ledford wrote:
> >
> >
> > Since Colin is non-responsive in this thread, I went ahead and took
> > his
> > patch, but then applied a fixup of my own:
>
> Sorry, I somehow missed that email. Thanks for following this up.
No worries. You're normally responsive, so that's why I said "in this
thread" and just took care of.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
WARNING: multiple messages have this Message-ID (diff)
From: Doug Ledford <dledford@redhat.com>
To: Colin Ian King <colin.king@canonical.com>,
Leon Romanovsky <leon@kernel.org>
Cc: Moni Shoua <monis@mellanox.com>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
linux-rdma@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IB/rxe: check for allocation failure on elem
Date: Mon, 09 Oct 2017 12:13:11 -0400 [thread overview]
Message-ID: <1507565591.46071.32.camel@redhat.com> (raw)
In-Reply-To: <a43bfb4f-e7c3-f6be-8946-952fb2d4af14@canonical.com>
On Mon, 2017-10-09 at 14:18 +0100, Colin Ian King wrote:
> On 09/10/17 14:16, Doug Ledford wrote:
> >
> >
> > Since Colin is non-responsive in this thread, I went ahead and took
> > his
> > patch, but then applied a fixup of my own:
>
> Sorry, I somehow missed that email. Thanks for following this up.
No worries. You're normally responsive, so that's why I said "in this
thread" and just took care of.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
next prev parent reply other threads:[~2017-10-09 16:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 14:37 [PATCH] IB/rxe: check for allocation failure on elem Colin King
2017-09-08 14:37 ` Colin King
[not found] ` <20170908143745.2445-1-colin.king-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2017-09-09 12:56 ` Leon Romanovsky
2017-09-09 12:56 ` Leon Romanovsky
2017-09-09 12:56 ` Leon Romanovsky
2017-09-12 14:48 ` Leon Romanovsky
2017-09-12 14:48 ` Leon Romanovsky
2017-10-09 13:16 ` Doug Ledford
2017-10-09 13:16 ` Doug Ledford
2017-10-09 13:18 ` Colin Ian King
2017-10-09 13:18 ` Colin Ian King
2017-10-09 16:13 ` Doug Ledford [this message]
2017-10-09 16:13 ` Doug Ledford
[not found] ` <1507554995.46071.25.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-09 13:43 ` Leon Romanovsky
2017-10-09 13:43 ` Leon Romanovsky
2017-10-09 13:43 ` 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=1507565591.46071.32.camel@redhat.com \
--to=dledford@redhat.com \
--cc=colin.king@canonical.com \
--cc=hal.rosenstock@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=monis@mellanox.com \
--cc=sean.hefty@intel.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 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.