From: haris iqbal <haris.phnx@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Sean Bruno <sbruno@freebsd.org>,
QEMU Developers <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v1] Changed malloc to g_malloc, free to g_free in bsd-user/qemu.h
Date: Wed, 4 May 2016 00:38:04 +0530 [thread overview]
Message-ID: <CAE_WKMy8psLGVykrG1mr+Tk4awRPsRoWjtkWKg12d6c00tX0_w@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9U5fshvjmTRBbsS9CMJMfyLwO799C2p9zYg9GkZWSaUA@mail.gmail.com>
On Wed, May 4, 2016 at 12:32 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 3 May 2016 at 19:10, haris iqbal <haris.phnx@gmail.com> wrote:
>> On Tue, May 3, 2016 at 11:02 PM, Sean Bruno <sbruno@freebsd.org> wrote:
>>> If this is the only patch needing review for the bsd-user code, please
>>> put me down as Reviewed by.
>>
>> Sorry, I am a newbie. Just to confirm, should I send the patch again
>> with "Reviewed by : Sean Bruno" line?
>
> No, you don't need to resend. When bsd-user patches are collected
> up to be applied then the person who does that will apply the
> reviewed-by tag.
>
> (If you needed to resend a patch for some other reason, then if
> the patch hasn't changed then you should add the reviewed-by
> tag when you resend it. But there's no need to resend purely to
> add the tag.)
Thanks for the reply, much appreciated.
>
> thanks
> -- PMM
--
With regards,
Md Haris Iqbal,
Placement Coordinator, MTech IT
NITK Surathkal,
Contact: +91 8861996962
prev parent reply other threads:[~2016-05-03 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 13:09 [Qemu-trivial] [Qemu-devel] [PATCH v1] Changed malloc to g_malloc, free to g_free in bsd-user/qemu.h Md Haris Iqbal
2016-05-03 9:45 ` haris iqbal
2016-05-03 17:32 ` Sean Bruno
2016-05-03 18:10 ` haris iqbal
2016-05-03 19:02 ` Peter Maydell
2016-05-03 19:08 ` haris iqbal [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=CAE_WKMy8psLGVykrG1mr+Tk4awRPsRoWjtkWKg12d6c00tX0_w@mail.gmail.com \
--to=haris.phnx@gmail.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sbruno@freebsd.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).