Thanks for checking. I'll wait for the tree to open back up again to
give others a chance to respond, and since it's not really related to
the split.
On 09/21/2012 10:49 AM, Lucas Meneghel Rodrigues wrote:
On Fri, Sep 21, 2012 at 11:48 AM, Lucas Meneghel Rodrigues
<[email protected]> wrote:
None that comes to mind, but a grep for nic_mode in the source code
will quickly tell us if there's something to worry about.
Ok, there's no place that uses it in the current upstream tree, so I'd
say it can be safely removed.
On Fri, Sep 21, 2012 at 10:52 AM, Chris Evich<[email protected]> wrote:
All,
I noticed we still are setting 'nic_mode = tap' despite my having tried to
remove it a while ago. The current design is such that both nettype=bridge
or nettype=network imply the use of a tap interface, so nic_mode = tap is
redundant (and possibly problematic if used). Does anyone know of a reason
this parameter needs to stick around?
--
Chris Evich, RHCA, RHCE, RHCDS, RHCSS
Quality Assurance Engineer
e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
--
Lucas
--
Chris Evich, RHCA, RHCE, RHCDS, RHCSS
Quality Assurance Engineer
e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
