From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42627) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZBqAs-000379-9N for qemu-devel@nongnu.org; Sun, 05 Jul 2015 16:06:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZBqAi-0002e0-Kx for qemu-devel@nongnu.org; Sun, 05 Jul 2015 16:06:02 -0400 Received: from mail-la0-x22b.google.com ([2a00:1450:4010:c03::22b]:33799) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZBqAi-0002dv-CZ for qemu-devel@nongnu.org; Sun, 05 Jul 2015 16:05:52 -0400 Received: by lagx9 with SMTP id x9so132466221lag.1 for ; Sun, 05 Jul 2015 13:05:51 -0700 (PDT) Message-ID: <55998E18.9010401@gmail.com> Date: Sun, 05 Jul 2015 23:05:44 +0300 From: Dmitry Osipenko MIME-Version: 1.0 References: <1435877531-24983-1-git-send-email-digetx@gmail.com> <1436110742-6190-1-git-send-email-digetx@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [v2] arm_mptimer fixes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Crosthwaite , Peter Maydell Cc: Paolo Bonzini , QEMU Developers 05.07.2015 22:52, Peter Crosthwaite пишет: > On Sun, Jul 5, 2015 at 8:39 AM, Dmitry Osipenko wrote: >> Hello, this is V2 of arm_mptimer patch series. Comments and suggestion from V1 >> has been addressed and the series was re-tested, including new test for IT bit >> masking/unmasking. >> >> [PATCH 1/2] arm_mptimer: Fix timer shutdown and mode change >> [PATCH v2 2/2] arm_mptimer: Respect IT bit state >> > > This looks like an ad-hoc cover letter. Use git to generate patch series covers. > > git format-patch HEAD~N --thread --cover-letter -vX > > For N patches version X of the series. > > Edit the 0000-cover-letter file with your cover mail contents and send > all the generated patches along with cover. > > This series doesn't show up in the patch tracking system due to irregular cover. > > Regards, > Peter > Thanks for advice, I used --compose --no-chain-reply-to. Please let me know if I should re-sent and sorry for the mess. -- Dmitry