search for: suceess

how do you manually cause a rollback in a transaction? I''ve looked everywhere with no suceess. Anyone know? Thanks in advance Chris -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrail...

...ount (it releases it again on failure), but because another code path may have obtained a reference. What about: "On error, the caller must call put_device on &@dev->dev (and not kfree), as another code path may have obtained a reference to @dev." > + * > + * Returns: 0 on suceess, -error on failure > + */ > int register_virtio_device(struct virtio_device *dev) > { > int err; > > dev->dev.bus = &virtio_bus; > + device_initialize(&dev->dev); > > /* Assign a unique device index and hence name. */ > err = ida_simple_get(...

...ount (it releases it again on failure), but because another code path may have obtained a reference. What about: "On error, the caller must call put_device on &@dev->dev (and not kfree), as another code path may have obtained a reference to @dev." > + * > + * Returns: 0 on suceess, -error on failure > + */ > int register_virtio_device(struct virtio_device *dev) > { > int err; > > dev->dev.bus = &virtio_bus; > + device_initialize(&dev->dev); > > /* Assign a unique device index and hence name. */ > err = ida_simple_get(...

I believe that I have incorporated all of the feedback given (thanks!). Changes since the 2008-11-16 version include: - ksh style & coding standards compliance in test script (Roland) - "dof_init_debug == B_FALSE" vs. "!dof_init_debug" (Adam) The updated webrev is at: http://cr.opensolaris.org/~mgerdts/6750659-2008-12-03/ -- Mike Gerdts http://mgerdts.blogspot.com/

Hi guys I have installed Xen 4 on Debian Lenny 5.0. I have a physical Windows 2003 Server and I wanna convert this server on a virtual server... I try to use XenConvert but without sucsess... Somebody can help??? Thanks Gilberto Nunes TI Selbetti Gestão de Documentos Telefone: +55 (47) 3441-6004 Celular: +55 (47) 8861-6672 _______________________________________________ Xen-users mailing

...emule, kaazaa , edonkey and so on works very good but ARES can''t connect. I''ve - iptables 1.3.3 - kernel 2.4.28 - ipp2p 0.8.0rc3 BUT, if I change policy iptables -P FORWARD ACCEPT ARES works, can connect. I''ve tried to guess tcp/udp ports with tcpdump without suceess. I guess that ipp2p only can block p2p on a ACCEPT policy firewall I must open some tcp/udp port ? Can anybody helpme ? bests andres.

...); +/** + * register_virtio_device - register virtio device + * @dev : virtio device interested + * + * If an error occurs, the caller must use put_device, instead of kfree, because + * device_initialize and device_add will increase @dev->dev's reference count. + * + * Returns: 0 on suceess, -error on failure + */ int register_virtio_device(struct virtio_device *dev) { int err; dev->dev.bus = &virtio_bus; + device_initialize(&dev->dev); /* Assign a unique device index and hence name. */ err = ida_simple_get(&virtio_index_ida, 0, 0, GFP_KERNEL); @@ -330,...

...ice on &@dev->dev (and not > kfree), as another code path may have obtained a reference to @dev." > It's good to understand, further more dev->name may has a bit mem leak. anyway, I'll correct all comments at V5. Thanks very much. >> + * >> + * Returns: 0 on suceess, -error on failure >> + */ >> int register_virtio_device(struct virtio_device *dev)

...r_virtio_driver); +/** + * register_virtio_device - register virtio device + * @dev : virtio device to be registered + * + * On error, the caller must call put_device on &@dev->dev (and not kfree), + * as another code path may have obtained a reference to @dev. + * + * Returns: 0 on suceess, -error on failure + */ int register_virtio_device(struct virtio_device *dev) { int err; dev->dev.bus = &virtio_bus; + device_initialize(&dev->dev); /* Assign a unique device index and hence name. */ err = ida_simple_get(&virtio_index_ida, 0, 0, GFP_KERNEL); @@ -330,...

Hi, The main change is split device_register into 2 sperate calls: device_initalize() and device_add, and then the caller can use put_device safety when fail to register_virtio_device. v3->v4: * split device_register into device_initialize and devicea_add that the caller can always use put_device when fail to register virtio device. v2->v3: * virtio: add new helper do get

Hi, The main change is split device_register into 2 sperate calls: device_initalize() and device_add, and then the caller can use put_device safety when fail to register_virtio_device. v3->v4: * split device_register into device_initialize and devicea_add that the caller can always use put_device when fail to register virtio device. v2->v3: * virtio: add new helper do get

Hello All Its first time i posting to this mail list :). I have done something (maybe) important. I write new IMQ device driver based from Martin Devera and Patrick McHardy implementation with device EOS support. My current implementation supporting only egress trafic shaping and kernel 2.4.25. For more details, source and examples have look at my page http://hyperfighter.jinak.cz/qos Ill