From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Andrei Errapart
<andrei-VvktuG2w+SIZux3j3Bed6fC9HSW9iNxf@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/4] Microsoft Visual C patches
Date: Thu, 19 Jun 2014 21:14:59 +1000 [thread overview]
Message-ID: <20140619111459.GM29264@voom.redhat.com> (raw)
In-Reply-To: <53A1C5FC.9040105-VvktuG2w+SIZux3j3Bed6fC9HSW9iNxf@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
On Wed, Jun 18, 2014 at 08:01:48PM +0300, Andrei Errapart wrote:
>
> commit b8ad167d89d7f5ba6398ffeab6a7f9ece954f208
> Author: Andrei Errapart <andrei-VvktuG2w+SIZux3j3Bed6fC9HSW9iNxf@public.gmane.org>
> Date: Wed Jun 18 18:43:17 2014 +0200
>
> * MSVC doesn't support 0-sized arrays.
Ugh, this is by far the ugliest of these workarounds, and the reason
for it in the code is really non-obvious. I'll have to think about
this some more.
> * Initialize check->inprogress, too.
Why..?
> Signed-off-by: Andrei Errapart <andrei-VvktuG2w+SIZux3j3Bed6fC9HSW9iNxf@public.gmane.org>
I've applied patches 2, 3, and 4. But for future reference, please remember:
* Patches should be inline, not attachments
* Commit message and signed-off-by lines should not be indented
* Commit messages need more details on the reason for the patch (see
the changes I've made for examples).
* Commit messages need a 1 line summary at the top (2, 3, and 4 have
this, but 1 doesn't)
* There should be a blank line between the 1-lite summary and the
remainder of the commit message
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-19 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-15 15:46 [PATCH] Microsoft Visual C patches Andrei Errapart
[not found] ` <539DBFC8.4050204-VvktuG2w+SIZux3j3Bed6fC9HSW9iNxf@public.gmane.org>
2014-06-16 10:46 ` David Gibson
[not found] ` <20140616104628.GB29264-1s0os16eZneny3qCrzbmXA@public.gmane.org>
2014-06-17 17:18 ` Matthew Gerlach
2014-06-18 17:01 ` [PATCH 1/4] " Andrei Errapart
[not found] ` <53A1C5FC.9040105-VvktuG2w+SIZux3j3Bed6fC9HSW9iNxf@public.gmane.org>
2014-06-19 11:14 ` David Gibson [this message]
[not found] ` <20140619111459.GM29264-1s0os16eZneny3qCrzbmXA@public.gmane.org>
2014-06-19 14:17 ` Andrei Errapart
[not found] ` <53A2F104.90701-VvktuG2w+SIZux3j3Bed6fC9HSW9iNxf@public.gmane.org>
2014-06-19 15:06 ` Andrei Errapart
2014-06-20 12:55 ` David Gibson
[not found] ` <20140620125528.GB16801-1s0os16eZneny3qCrzbmXA@public.gmane.org>
2014-06-20 13:32 ` Simon Glass
2014-06-18 17:02 ` [PATCH 2/4] " Andrei Errapart
2014-06-18 17:03 ` [PATCH 3/4] " Andrei Errapart
2014-06-18 17:04 ` [PATCH 4/4] " Andrei Errapart
2014-06-18 17:27 ` [PATCH] " Andrei Errapart
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=20140619111459.GM29264@voom.redhat.com \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=andrei-VvktuG2w+SIZux3j3Bed6fC9HSW9iNxf@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).