[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegupwNbVPenZdMX8F2Z3vKSJdfAsXuiF4YA+nbnj2Kp=sw@mail.gmail.com>
Date: Wed, 24 Apr 2019 15:19:11 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Kirill Smelkov <kirr@...edi.com>
Cc: Miklos Szeredi <mszeredi@...hat.com>,
Han-Wen Nienhuys <hanwen@...gle.com>,
Jakob Unterwurzacher <jakobunt@...il.com>,
Kirill Tkhai <ktkhai@...tuozzo.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
fuse-devel <fuse-devel@...ts.sourceforge.net>,
stable <stable@...r.kernel.org>
Subject: Re: [RESEND4, PATCH 1/2] fuse: retrieve: cap requested size to
negotiated max_write
On Wed, Apr 24, 2019 at 2:31 PM Kirill Smelkov <kirr@...edi.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
Powered by blists - more mailing lists