qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Mriyam Tamuli <mbtamuli@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] Converted malloc calls to g_malloc and g_new
Date: Sat, 12 Mar 2016 21:40:20 +0100	[thread overview]
Message-ID: <56E47EB4.4020809@weilnetz.de> (raw)
In-Reply-To: <CAPD4N6O=mwcohf87Na6oVb8xoNqGthP=CYWzEvUBq8DreDvkPA@mail.gmail.com>

Am 12.03.2016 um 18:53 schrieb Mriyam Tamuli:
> Thanks a lot for the feedback. I will do as you suggested. I have two
> more questions, though -
> 
> 1. So after a patch is submitted, there will be a review in sometime by
> someone? Is that how I will come to know if my changes are correct?

Yes, that's how it should work. But it can also happen that a patch
does not get any attention. In that case you can send a polite reminder.

See http://wiki.qemu.org/Contribute/SubmitAPatch for more important
information on submitting patches.

> 
> 2. If I split the patch into smaller parts and send to qemu-trivial, do
> I need to cc qemu-devel?

Yes, trivial patches should be sent to qemu-trivial, qemu-devel and
any maintainers of the modified code.

Stefan

  reply	other threads:[~2016-03-12 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-12 11:51 [Qemu-devel] [PATCH 1/1] Converted malloc calls to g_malloc and g_new Mriyam Tamuli
2016-03-12 16:38 ` Mriyam Tamuli
2016-03-13  8:12   ` Alex Bennée
2016-03-12 17:20 ` Stefan Weil
2016-03-12 17:53   ` Mriyam Tamuli
2016-03-12 20:40     ` Stefan Weil [this message]
2016-03-13  8:17     ` Alex Bennée
2016-03-13  8:10 ` Alex Bennée

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=56E47EB4.4020809@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=mbtamuli@gmail.com \
    --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).