Date: Thu, 11 Oct 2012 14:53:28 -0500 From: Mark Felder <feld@feld.me> To: freebsd-xen@freebsd.org, =?ISO-8859-1?q?G=F3t_Andr=E1s?= <got.andras@deployis.eu> Subject: Re: xenbusb_nop_confighook_cb timeout Message-ID: <op.wl05jeqn34t2sn@tech304> In-Reply-To: <5075E641.20409@deployis.eu> References: <50757ADA.7060101@deployis.eu> <88AB8E8E-0D6C-4ED7-B0DC-7466DB7D3634@ramattack.net> <F826C6FD-AE9C-46A5-9029-85D79B1B937C@ramattack.net> <op.wly779dz34t2sn@tech304> <E8FB52A5-FCB8-4773-814A-72D4F44B03F2@ramattack.net> <5075E641.20409@deployis.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 10 Oct 2012 16:18:57 -0500, G=C3=B3t Andr=C3=A1s <got.andras@depl= oyis.eu> =20 wrote: > The patched worked for me also. I hope somehow it'll make to into = 9.1rc =20 > if send a reply to the previous PR. Can we get a confirmation from any devs about whether or not this patch = is =20 the "right way" to fix it? If so, I'd also appreciate seeing this slip =20 into 9.1 so the latest stable FreeBSD release works reliably with the =20 latest stable XenServer/XCP release...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wl05jeqn34t2sn>