From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51172)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mdavidsaver@gmail.com>) id 1ZkMQ1-00062I-St
	for qemu-devel@nongnu.org; Thu, 08 Oct 2015 21:24:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mdavidsaver@gmail.com>) id 1ZkMPz-0007j5-5A
	for qemu-devel@nongnu.org; Thu, 08 Oct 2015 21:24:21 -0400
Received: from mail-qg0-x229.google.com ([2607:f8b0:400d:c04::229]:34648)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mdavidsaver@gmail.com>) id 1ZkMPz-0007j1-1R
	for qemu-devel@nongnu.org; Thu, 08 Oct 2015 21:24:19 -0400
Received: by qgez77 with SMTP id z77so57740448qge.1
	for <qemu-devel@nongnu.org>; Thu, 08 Oct 2015 18:24:17 -0700 (PDT)
Message-ID: <56171740.2000809@gmail.com>
Date: Thu, 08 Oct 2015 21:24:16 -0400
From: Michael Davidsaver <mdavidsaver@gmail.com>
MIME-Version: 1.0
References: <cover.1444318183.git.mdavidsaver@gmail.com>
	<CAPokK=pUch7OjFoCBjrt9o2moDywbPtg+mn0xj2RbBO8Dq+zaQ@mail.gmail.com>
In-Reply-To: <CAPokK=pUch7OjFoCBjrt9o2moDywbPtg+mn0xj2RbBO8Dq+zaQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] Exit on reset for armv7-m
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>

On 10/08/2015 04:09 PM, Peter Crosthwaite wrote:
> On Thu, Oct 8, 2015 at 8:40 AM, Michael Davidsaver
> <mdavidsaver@gmail.com> wrote:
>> Implement the SYSRESETREQ bit of the AIRCR register
>> for armv7-m (ie. cortex-m3).
>>
> 
> This would serve better as the commit message to the patch (which I
> notice is missing a commit blurb).

Does this warrant sending an updated patch?  I would have no objection to whomever applies the patch simply changing the commit message.

>> A small patch to see if I have the submission process figured out.
>>
> 
> It is usual for the cover and patches to be enumerated together with
> the cover being patch 0, e.g. the subject would read [PATCH 0/1]. the
> --cover-letter switch of git format-patch does this for you.

Alas in this case it did not.  Probably because I omitted '--numbered'.

>> Michael Davidsaver (1):
> 
> When sending a single, a cover is not required. You could just send
> the patch on it's own. This will all be useful when you come to send
> multi-patch series however.

Noted.

Thanks for the feedback Peter.


Michael