From: "Andreas Färber" <afaerber@suse.de>
To: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
monstr@monstr.eu, edgar.iglesias@petalogix.com,
qemu-devel@nongnu.org, duyl@xilinx.com, linnj@xilinx.com,
john.williams@petalogix.com
Subject: Re: [Qemu-devel] [RFC PATCH 5/7] vl.c: added -kerndtb option
Date: Tue, 24 Jan 2012 08:50:05 +0100 [thread overview]
Message-ID: <4F1E62AD.5020905@suse.de> (raw)
In-Reply-To: <CAEgOgz7jWeMVwQ8h30TS2LFye+pn1SC=AUR6MX5ftkL2AfS-aw@mail.gmail.com>
Hi Peter,
Am 24.01.2012 08:35, schrieb Peter Crosthwaite:
> Thanks for that, I will rename the switch to -kernel-dtb.
>
> You are correct that 7/7 should have the usage in it, that patch was
> incorrectly generated, I will regenerate and resend the series tomorrow
> for another review cycle.
Just found it, sorry. Is it just my mail client or did something go
wrong with sending? 0/7 is not threaded with the rest, and neither is
the fixed-up 7/7. It would facilitate review.
When resending, please also cc our ARM maintainer, even if your Edgar
might be the one to commit it in the end.
Please also don't forget to update MAINTAINERS with an entry for the new
machine and devices.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-01-24 7:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 7:20 [Qemu-devel] [RFC PATCH 0/7] Zynq-7000 EPP platform model Peter A. G. Crosthwaite
[not found] ` <cover.1327302677.git.peter.crosthwaite@petalogix.com>
2012-01-23 7:20 ` [Qemu-devel] [RFC PATCH 1/7] cadence_uart: first revision Peter A. G. Crosthwaite
2012-01-24 2:02 ` John Linn
2012-01-24 8:07 ` Andreas Färber
2012-01-23 7:20 ` [Qemu-devel] [RFC PATCH 2/7] cadence ttc: " Peter A. G. Crosthwaite
2012-01-24 2:03 ` John Linn
2012-01-23 7:20 ` [Qemu-devel] [RFC PATCH 3/7] cadence_wdt: " Peter A. G. Crosthwaite
2012-01-24 2:03 ` John Linn
2012-01-23 7:20 ` [Qemu-devel] [RFC PATCH 4/7] cadence_gem: " Peter A. G. Crosthwaite
2012-01-24 2:05 ` John Linn
2012-01-23 7:20 ` [Qemu-devel] [RFC PATCH 5/7] vl.c: added -kerndtb option Peter A. G. Crosthwaite
2012-01-24 7:22 ` Andreas Färber
2012-01-24 7:35 ` Peter Crosthwaite
2012-01-24 7:50 ` Andreas Färber [this message]
2012-01-24 18:23 ` Stefan Weil
2012-01-26 19:34 ` Scott Wood
2012-01-26 21:27 ` Eric Blake
2012-01-27 8:25 ` Markus Armbruster
2012-01-29 6:51 ` Peter Crosthwaite
2012-01-30 0:28 ` John Williams
2012-01-30 0:33 ` John Williams
2012-01-30 2:11 ` Anthony Liguori
2012-01-30 2:19 ` John Williams
2012-01-30 2:28 ` Anthony Liguori
2012-01-30 2:41 ` John Williams
2012-01-30 2:48 ` Anthony Liguori
2012-02-01 2:06 ` John Williams
2012-01-30 2:10 ` Anthony Liguori
2012-01-26 19:40 ` Peter Maydell
2012-01-23 7:20 ` [Qemu-devel] [RFC PATCH 6/7] arm_boot: added initrd address override Peter A. G. Crosthwaite
2012-01-23 7:20 ` [Qemu-devel] [RFC PATCH 7/7] xilinx_zynq: machine model first revision Peter A. G. Crosthwaite
2012-01-23 8:00 ` Michal Simek
2012-01-23 8:22 ` Peter Crosthwaite
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=4F1E62AD.5020905@suse.de \
--to=afaerber@suse.de \
--cc=duyl@xilinx.com \
--cc=edgar.iglesias@petalogix.com \
--cc=john.williams@petalogix.com \
--cc=linnj@xilinx.com \
--cc=monstr@monstr.eu \
--cc=peter.crosthwaite@petalogix.com \
--cc=peter.maydell@linaro.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).