From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagig@dev.mellanox.co.il>
Cc: Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, Stable <stable@vger.kernel.org>
Subject: Re: [PATCH] IB/srp: Fix possible send queue overflow
Date: Sun, 22 Nov 2015 05:37:04 -0800 [thread overview]
Message-ID: <20151122133704.GA22831@infradead.org> (raw)
In-Reply-To: <5641C859.6070107@dev.mellanox.co.il>
On Tue, Nov 10, 2015 at 12:35:05PM +0200, Sagi Grimberg wrote:
> >Are you planning to pick this up? Note that this patch
> >is stable material as well.
>
> Doug? any plans for this patch?
We should really get this in an into -stable. Bart, can you resend
the series and if it doesn't get picked up next week send it directly
to Linus?
next prev parent reply other threads:[~2015-11-22 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 9:26 [PATCH] IB/srp: Fix possible send queue overflow Sagi Grimberg
2015-10-15 15:35 ` Bart Van Assche
2015-11-03 18:56 ` Sagi Grimberg
2015-11-05 10:23 ` Sagi Grimberg
2015-11-10 10:35 ` Sagi Grimberg
2015-11-22 13:37 ` Christoph Hellwig [this message]
2015-11-24 1:11 ` Bart Van Assche
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=20151122133704.GA22831@infradead.org \
--to=hch@infradead.org \
--cc=dledford@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=sagig@dev.mellanox.co.il \
--cc=stable@vger.kernel.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).