From: Eric Blake <eblake@redhat.com>
To: John Bradley <flypie1@yahoo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "John Bradley" <flypie@rocketmail.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Geert Martin Ijewski" <gm.ijewski@web.de>,
"Markus Armbruster" <armbru@redhat.com>,
"Alistair Francis" <alistair.francis@xilinx.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] Add Markus Armbrusters code for Broadcom Perhiperals for ARM.
Date: Wed, 17 May 2017 20:52:29 -0500 [thread overview]
Message-ID: <39e1208c-9ed4-6c56-76d1-e5a7e46a409d@redhat.com> (raw)
In-Reply-To: <684185116.2952708.1495044580181@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2332 bytes --]
On 05/17/2017 01:09 PM, John Bradley via Qemu-devel wrote:
> Also available at
>
> https://www.dropbox.com/s/gwuquw0kirstw7a/0001-Add-Markus-Armbrusters-code-for-Broadcom-Perhiperals.patch?dl=0
>
> Following suggestions split my original patch up. This the largest monolithic chunk is
> additional BCM device support from Markus Armbruster.
>
>
>>From 0b39a04030d5a2cea4fcd2159d365580ca155b78 Mon Sep 17 00:00:00 2001
> From: John Bradley <flypie@rocketmail.com>
> Date: Wed, 17 May 2017 18:57:21 +0100
> Subject: [PATCH] Add Markus Armbrusters code for Broadcom Perhiperals for ARM.
>
> Signed-off-by: John Bradley <flypie@rocketmail.com>
> ---
After a break from the keyboard (always a good idea), I've re-read my
comments on this thread so far. As usual, email is a lousy medium for
conveying emotion and intent, and I can see how my curt replies merely
pointing out ways that you can improve your patch can easily be
misconstrued as negative advice or rejection of the idea in general. So
let me take this time to apologize if I've come across as over-harsh,
and give you a big thanks for your efforts to contribute; your additions
have the potential to make qemu better. I hope that we do not scare you
off with advice on improving your contributions up to community
standard, but that you feel welcome to contribute to the community, as
well as using the give-and-take iteration of review to make your first
patch great. Writing a first patch series can be especially daunting
when you are new to an unfamiliar process, and while we were all once at
your point, it takes effort to remember that not everyone is as familiar
with open source ways, and how it felt on our own first patch submission.
A big hint: the great way to get a patch accepted on ANY project is to
first offer reviews on other patches being submitted to the list.
Review backlog is always present, but it gets especially bad if there
are more contributors than reviewers. Plus, reviewing code that other
people write can give you a feel for what constitutes a typical patch
for the project, which will let you model your own submissions in the
same style.
Good luck!
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2017-05-18 1:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <684185116.2952708.1495044580181.ref@mail.yahoo.com>
2017-05-17 18:09 ` [Qemu-devel] Add Markus Armbrusters code for Broadcom Perhiperals for ARM John Bradley
2017-05-17 18:27 ` Eric Blake
2017-05-17 18:34 ` John Bradley
2017-05-17 19:11 ` Eric Blake
2017-05-17 20:53 ` John Bradley
2017-05-17 21:15 ` Eric Blake
2017-05-17 21:25 ` John Bradley
2017-05-17 21:55 ` Eric Blake
2017-05-18 7:47 ` Markus Armbruster
2017-05-18 16:39 ` John Bradley
2017-05-17 19:04 ` John Snow
2017-05-18 1:52 ` Eric Blake [this message]
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=39e1208c-9ed4-6c56-76d1-e5a7e46a409d@redhat.com \
--to=eblake@redhat.com \
--cc=alistair.francis@xilinx.com \
--cc=armbru@redhat.com \
--cc=f4bug@amsat.org \
--cc=flypie1@yahoo.com \
--cc=flypie@rocketmail.com \
--cc=gm.ijewski@web.de \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).