qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Martin Galvan <martin.galvan@tallertechnologies.com>,
	qemu-devel@nongnu.org, peter.maydell@linaro.org,
	pbonzini@redhat.com, edgar.iglesias@gmail.com, rth@twiddle.net,
	aurelien@aurel32.net, kraxel@redhat.com, blauwirbel@gmail.com,
	lcapitulino@redhat.com, armbru@redhat.com, afaerber@suse.de,
	dmitry@daynix.com
Subject: Re: [Qemu-devel] [PATCH v2 02/13] Use unsigned types for the 'len' argument of all memory read/write functions
Date: Tue, 1 Mar 2016 09:11:18 -0700	[thread overview]
Message-ID: <56D5BF26.7030802@redhat.com> (raw)
In-Reply-To: <1456847859-4771-2-git-send-email-martin.galvan@tallertechnologies.com>

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

On 03/01/2016 08:57 AM, Martin Galvan wrote:

Missing S-o-b. Patch subject line is identical to 1/13, which is a no-no
(if I'm backporting a patch, I want the subject line to be sufficient to
determine which patch I'm backporting, and not give me 13 candidates);
please resubmit the series with distinct subject lines (adding an
appropriate prefix for each maintainer that you are targetting will help).

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2016-03-01 16:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1456847650-4476-1-git-send-email-martin.galvan@tallertechnologies.com>
2016-03-01 15:57 ` [Qemu-devel] [PATCH v2 01/13] Use unsigned types for the 'len' argument of all memory read/write functions Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 02/13] " Martin Galvan
2016-03-01 16:11     ` Eric Blake [this message]
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 03/13] " Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 04/13] " Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 05/13] " Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 06/13] " Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 07/13] " Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 08/13] " Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 09/13] " Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 10/13] " Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 11/13] " Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 12/13] " Martin Galvan
2016-03-01 15:57   ` [Qemu-devel] [PATCH v2 13/13] " Martin Galvan
2016-03-01 16:05   ` [Qemu-devel] [PATCH v2 01/13] " Eric Blake
2016-03-01 17:56     ` Martin Galvan

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=56D5BF26.7030802@redhat.com \
    --to=eblake@redhat.com \
    --cc=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=aurelien@aurel32.net \
    --cc=blauwirbel@gmail.com \
    --cc=dmitry@daynix.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=martin.galvan@tallertechnologies.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).