From: Gerhard Wiesinger <lists@wiesinger.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin O'Connor <kevin@koconnor.net>,
qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] network: Added option to disable NIC option roms
Date: Sun, 8 Jan 2012 21:56:20 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1201082149400.545@bbs.intern> (raw)
In-Reply-To: <CAJSP0QXCtZ+WMjY+YOQs53NJsUM44N=W+KLiKOa+vdS2_k=8GA@mail.gmail.com>
On Sun, 8 Jan 2012, Stefan Hajnoczi wrote:
> On Sun, Jan 8, 2012 at 11:55 AM, Gerhard Wiesinger <lists@wiesinger.com> wrote:
>> Option ROM for network interface cards (NICs) can now explicitly disabled
>> with romfile=disabled parameter. With hotplugable NICs (currently NE2000,
>> PCNET)
>> romfile=(empty) didn't work. This patch disables Option ROMs for iPXE for
>> alls
>> supported NICs (hotplugable and non hotplugable).
>>
>> Examples with 2 NICs with disabled Option ROM (separated on different lines
>> for readability):
>> -device rtl8139,mac=1a:46:0b:ca:bc:7c,vlan=0,romfile=disabled
>> -net tap,ifname=tap0,script=no,downscript=no,vlan=0
>> -device pcnet,mac=1a:46:0b:ca:bc:7e,vlan=1,romfile=disabled
>> -net tap,ifname=tap1,script=no,downscript=no,vlan=1
>
> Did you consider "no" or "none"? Those are already used by -net
> script=no and -vga none. I'm afraid we don't have much consistency in
> the command-line and adding more variants of basically the same
> concept should be avoided when possible.
Whether the option is spelled "disabled", "no", "none" or all of them
above: I don't care about that, just the group of maintainers should
decide (I would prefer all of them ...).
The only thing: just help me with git and doing another commit and
preparing V2 patch then ...
# I did:
git stash save mypatch
git branch -b mybranch lastcommit
# can be optimized with -b option ...
git checkout mybranch
git stash pop
git merge --squash master
git commit -a -F - <<EOF
commit message
EOF
# Signoff must be added
git format-patch -s master
git checkout master
# Send mail
Ciao,
Gerhard
--
http://www.wiesinger.com/
next prev parent reply other threads:[~2012-01-08 20:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 11:55 [Qemu-devel] [PATCH] network: Added option to disable NIC option roms Gerhard Wiesinger
2012-01-08 16:40 ` Stefan Hajnoczi
2012-01-08 20:56 ` Gerhard Wiesinger [this message]
2012-01-09 8:06 ` Stefan Hajnoczi
2012-01-09 9:15 ` Gerd Hoffmann
2012-01-12 6:45 ` Gerhard Wiesinger
2012-01-12 7:58 ` Gerd Hoffmann
2012-01-25 21:08 ` Gerhard Wiesinger
-- strict thread matches above, loose matches on Subject: below --
2012-01-25 21:01 Gerhard Wiesinger
2012-01-26 7:45 ` Markus Armbruster
2012-01-26 10:45 ` Gerd Hoffmann
2012-01-26 11:00 ` Markus Armbruster
2012-01-27 6:56 ` Gerhard Wiesinger
2012-01-27 16:02 ` Gerhard Wiesinger
2012-02-13 6:23 ` Gerhard Wiesinger
2012-02-16 6:41 ` Gerhard Wiesinger
2012-02-01 22:19 ` Anthony Liguori
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=alpine.LFD.2.02.1201082149400.545@bbs.intern \
--to=lists@wiesinger.com \
--cc=gleb@redhat.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).