From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: Benjamin LaHaise <bcrl@kvack.org>, Jeff Moyer <jmoyer@redhat.com>
Cc: viro@zeniv.linux.org.uk, linux-aio@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RESEND] fs: aio: fix the increment of aio-nr and counting against aio-max-nr
Date: Fri, 14 Jul 2017 20:58:28 -0300 [thread overview]
Message-ID: <276da3a6-299c-0006-fa6f-9ab3120616ba@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170706210718.GD8658@kvack.org>
Hi Ben,
On 07/06/2017 06:07 PM, Benjamin LaHaise wrote:
> I'm queuing this up in my aio-next and will push upstream after a few days
> of soaking in linux-next.
Apparently this patch could only make linux-next in today's tree (0714)
as seen in [1], and the merge window should close in 2 days (Jul, 16th)
according to LWN [2].
Wondering if you'd consider submitting it to the few initial v4.13-rcs ?
(after the testing period you mentioned) so that it can make v4.13, as
it can be considered a fix too, not just an improvement, IMHO :- )
Thank you.
[1] https://lkml.org/lkml/2017/7/13/888
[2] https://lwn.net/Articles/727385/
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
next prev parent reply other threads:[~2017-07-14 23:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 13:53 [PATCH RESEND] fs: aio: fix the increment of aio-nr and counting against aio-max-nr Mauricio Faria de Oliveira
2017-07-05 13:59 ` Mauricio Faria de Oliveira
2017-07-05 19:28 ` Jeff Moyer
2017-07-06 21:07 ` Benjamin LaHaise
2017-07-06 22:25 ` Jeff Moyer
2017-07-07 12:44 ` Mauricio Faria de Oliveira
2017-07-14 23:58 ` Mauricio Faria de Oliveira [this message]
2017-09-07 3:04 ` Mauricio Faria de Oliveira
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=276da3a6-299c-0006-fa6f-9ab3120616ba@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=bcrl@kvack.org \
--cc=jmoyer@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).