From: Kirill Smelkov <kirr@nexedi.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Miklos Szeredi <mszeredi@redhat.com>, <gluster-devel@gluster.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Sander Eikelenboom <linux@eikelenboom.it>,
Han-Wen Nienhuys <hanwen@google.com>,
Jakob Unterwurzacher <jakobunt@gmail.com>
Subject: Re: [PATCH, RESEND3] fuse: require /dev/fuse reads to have enough buffer capacity (take 2)
Date: Thu, 01 Aug 2019 13:50:02 +0000 [thread overview]
Message-ID: <20190801134955.GA18544@deco.navytux.spb.ru> (raw)
In-Reply-To: <CAJfpegscn7B+TrD5hckXkpHEb_62m6O9-kFOOehWyC89CPFunw@mail.gmail.com>
On Thu, Aug 01, 2019 at 12:35:03PM +0200, Miklos Szeredi wrote:
> On Wed, Jul 24, 2019 at 11:46 AM Kirill Smelkov <kirr@nexedi.com> wrote:
> >
> > Miklos,
> >
> > I was sending this patch for ~1.5 month without any feedback from you[1,2,3].
> > The patch was tested by Sander Eikelenboom (original GlusterFS problem
> > reporter)[4], and you said that it will be ok to retry for next
> > cycle[5]. I was hoping for this patch to be picked up for 5.3 and queued
> > to Linus's tree, but in despite several resends from me (the same patch;
> > just reminders) nothing is happening. v5.3-rc1 came out on last Sunday,
> > which, in my understanding, denotes the close of 5.3 merge window. What
> > is going on? Could you please pick up the patch and handle it?
>
> Applied.
Thanks...
prev parent reply other threads:[~2019-08-01 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 9:46 Kirill Smelkov
2019-08-01 10:35 ` Miklos Szeredi
2019-08-01 13:50 ` Kirill Smelkov [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=20190801134955.GA18544@deco.navytux.spb.ru \
--to=kirr@nexedi.com \
--cc=gluster-devel@gluster.org \
--cc=hanwen@google.com \
--cc=jakobunt@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.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
all inboxes | Powered by JetHome®