From: Laurent Vivier <Laurent.Vivier@bull.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2][UPDATE] remove unused parameters from QEMUMachineInitFunc
Date: Mon, 12 Nov 2007 17:36:09 +0100 [thread overview]
Message-ID: <1194885369.8525.5.camel@frecb07144> (raw)
In-Reply-To: <f43fc5580711120823h5735c445yef5da7dc325da7c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]
Le lundi 12 novembre 2007 à 18:23 +0200, Blue Swirl a écrit :
> On 11/12/07, Laurent Vivier <Laurent.Vivier@bull.net> wrote:
> >
> > It appears that fd_filename and snapshot are not needed/used by machine
> > init functions (QEMUMachineInitFunc).
> >
> > This patch removes them.
>
> I don't know what was the idea for these parameters, so I can't
> comment on the correctness of the patch in general.
fd_filename cannot be managed because I suppressed the array in vl.c
and Fabrice (when he commented the first revision of this patch)
proposed to remove "snapshot" too:
"- While modifying the machine init function, you can suppress the
snapshot parameter."
> > /* SPARCstation 5 hardware initialisation */
> > -static void ss5_init(int RAM_size, int vga_ram_size, const char *boot_device,
> > - DisplayState *ds, const char **fd_filename, int snapshot,
> > +static void ss5_init(int RAM_size, int vga_ram_size,
> > + const char *boot_device, DisplayState *ds,
> > const char *kernel_filename, const char *kernel_cmdline,
> > const char *initrd_filename, const char *cpu_model)
> > {
> > @@ -616,8 +616,8 @@ static void ss5_init(int RAM_size, int v
> > }
> >
> > /* SPARCstation 10 hardware initialisation */
> > -static void ss10_init(int RAM_size, int vga_ram_size, const char *boot_device,
> > - DisplayState *ds, const char **fd_filename, int snapshot,
> > +static void ss10_init(int RAM_size, int vga_ram_size,
> > + const char *boot_device, DisplayState *ds,
> > const char *kernel_filename, const char *kernel_cmdline,
> > const char *initrd_filename, const char *cpu_model)
>
> You didn't fix ss600mp_init, which was added yesterday.
Oops, sorry, I missed it.
Thank you for your comments,
Laurent
--
------------- Laurent.Vivier@bull.net --------------
"In short: just say NO TO DRUGS and maybe you won't
end up like the Hurd people." -- Linus Torvald
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-12 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 15:05 [Qemu-devel] [PATCH 0/2][UPDATE] Add "-drive" parameter Laurent Vivier
2007-11-12 15:05 ` [Qemu-devel] [PATCH 1/2][UPDATE] remove unused parameters from QEMUMachineInitFunc Laurent Vivier
2007-11-12 15:05 ` [Qemu-devel] [PATCH 2/2][UPDATE] Add arg -drive to define new drive with more features Laurent Vivier
2007-11-12 16:44 ` Blue Swirl
2007-11-12 16:53 ` Laurent Vivier
2007-11-13 16:02 ` Laurent Vivier
2007-11-13 20:50 ` Blue Swirl
2007-11-13 21:22 ` Laurent Vivier
2007-11-12 16:23 ` [Qemu-devel] [PATCH 1/2][UPDATE] remove unused parameters from QEMUMachineInitFunc Blue Swirl
2007-11-12 16:36 ` Laurent Vivier [this message]
2007-11-12 17:14 ` Laurent Vivier
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=1194885369.8525.5.camel@frecb07144 \
--to=laurent.vivier@bull.net \
--cc=blauwirbel@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).