From: Miklos Szeredi <miklos@szeredi.hu>
To: Kirill Smelkov <kirr@nexedi.com>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
Han-Wen Nienhuys <hanwen@google.com>,
Jakob Unterwurzacher <jakobunt@gmail.com>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
fuse-devel <fuse-devel@lists.sourceforge.net>,
stable <stable@vger.kernel.org>
Subject: Re: [RESEND4, PATCH 1/2] fuse: retrieve: cap requested size to negotiated max_write
Date: Wed, 24 Apr 2019 15:19:11 +0200 [thread overview]
Message-ID: <CAJfpegupwNbVPenZdMX8F2Z3vKSJdfAsXuiF4YA+nbnj2Kp=sw@mail.gmail.com> (raw)
In-Reply-To: <20190424123107.GA32024@deco.navytux.spb.ru>
On Wed, Apr 24, 2019 at 2:31 PM Kirill Smelkov <kirr@nexedi.com> wrote:
> Thanks. Does it mean that the patch is ok? Do I need to rework
> something?
Pushed to #for-next with all the rest. Made some changes to the
patches, so please verify.
> I see. Probably it is not "quoted-printable" as
>
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: 8bit
Well, google converts it to quoted-printable then:
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
> suggests and it is maybe due to UTF-8 characters (I used "·" several
> times in patch description).
Please refrain from gratuitous use of non-ascii. That middle-dot is
written as "*" in C (fixed the patch description).
Thanks,
Miklos
next prev parent reply other threads:[~2019-04-24 13:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 10:15 [RESEND4, PATCH 0/2] fuse: don't stuck clients on retrieve_notify with size > max_write Kirill Smelkov
2019-03-27 10:15 ` [RESEND4, PATCH 2/2] fuse: require /dev/fuse reads to have enough buffer capacity as negotiated Kirill Smelkov
2019-04-24 10:48 ` Miklos Szeredi
2019-04-24 11:58 ` Kirill Smelkov
2019-03-27 10:15 ` [RESEND4, PATCH 1/2] fuse: retrieve: cap requested size to negotiated max_write Kirill Smelkov
2019-04-24 10:44 ` Miklos Szeredi
2019-04-24 11:56 ` Kirill Smelkov
2019-04-24 12:17 ` Miklos Szeredi
2019-04-24 12:31 ` Kirill Smelkov
2019-04-24 13:19 ` Miklos Szeredi [this message]
2019-04-24 14:22 ` Kirill Smelkov
2019-04-24 15:02 ` Miklos Szeredi
2019-04-24 18:10 ` Kirill Smelkov
2019-04-24 18:59 ` Kirill Smelkov
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='CAJfpegupwNbVPenZdMX8F2Z3vKSJdfAsXuiF4YA+nbnj2Kp=sw@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=akpm@linux-foundation.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hanwen@google.com \
--cc=jakobunt@gmail.com \
--cc=kirr@nexedi.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--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).