From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34130) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKdiQ-0002HS-Gn for qemu-devel@nongnu.org; Mon, 03 Mar 2014 20:00:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WKdiI-0003bJ-3Q for qemu-devel@nongnu.org; Mon, 03 Mar 2014 20:00:14 -0500 Received: from mail-pb0-x229.google.com ([2607:f8b0:400e:c01::229]:50235) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKdiH-0003Xl-T1 for qemu-devel@nongnu.org; Mon, 03 Mar 2014 20:00:06 -0500 Received: by mail-pb0-f41.google.com with SMTP id jt11so4475431pbb.14 for ; Mon, 03 Mar 2014 17:00:04 -0800 (PST) Message-ID: <5315258E.1000109@gmail.com> Date: Tue, 04 Mar 2014 08:59:58 +0800 From: Chen Gang MIME-Version: 1.0 References: <52EF68CA.9060604@gmail.com> <20140203103429.GB10408@redhat.com> <52EF71DC.3000309@gmail.com> <52F0C8BA.7020709@gmail.com> <20140204110631.GD5632@redhat.com> <52F0CD67.5070601@gmail.com> <87siry3l7t.fsf@linux.vnet.ibm.com> <52F17B5E.1050602@gmail.com> <52FF3182.9090106@gmail.com> <53097D8E.1030803@gmail.com> <87sir850ho.fsf@blackfin.pond.sub.org> <87ha7o3c5x.fsf@blackfin.pond.sub.org> <530FCBAD.10305@gmail.com> <531219CC.4050505@gmail.com> <5314BF54.4060909@redhat.com> In-Reply-To: <5314BF54.4060909@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/3] hw/9pfs: fix 3 issues which related with path string List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake , Markus Armbruster , "Aneesh Kumar K.V" , aliguori@amazon.com, "Daniel P. Berrange" Cc: QEMU Developers On 03/04/2014 01:43 AM, Eric Blake wrote: > On 03/01/2014 10:33 AM, Chen Gang wrote: >> Patch 1/3: move v9fs_string_free() to below "err_out:" >> >> Patch 2/3: use snprintf() instead of sprintf() >> (which will be replaced of by Path 3/3) >> >> Patch 3/3: use g_strdup_printf() instead of PATH_MAX limitation > > By sending this series as a deeply nested reply (14 References: > listings), it's harder to note that it is an independent series. It's > best to send your 0/N cover letter as a new top-level thread, rather > than burying it an existing thread. > OK, thanks. My current 0/N patch is almost useless, it really should/need provide some more useful information. Next time, when I send a new series, I shall/need reference the 0/N cover letter of another members' series, firstly. Thanks -- Chen Gang Open, share, and attitude like air, water, and life which God blessed