Displaying 20 results from an estimated 169 matches for "finalised".
Did you mean:
finalise
2015 Jun 25
2
[PATCH v2] v2v: Free XML objects in the correct order.
In version 2:
- No substantial change, I just tidied up the code a bit.
- Removed one case where whitespace changes had crept in.
Rich.
2015 Jun 25
0
[PATCH v2] v2v: Free XML objects in the correct order.
If you free an xmlDocPtr before any xmlXPathObjectPtrs that reference
the doc, you'll get valgrind errors like this:
==7390== Invalid read of size 4
==7390== at 0x4EB8BC6: xmlXPathFreeNodeSet (xpath.c:4185)
==7390== by 0x4EB8CC5: xmlXPathFreeObject (xpath.c:5492)
==7390== by 0x400A56: main (in /tmp/test)
==7390== Address 0x60c0928 is 8 bytes inside a block of size 120
2015 Jun 25
0
[PATCH] v2v: Free XML objects in the correct order.
If you free an xmlDocPtr before any xmlXPathObjectPtr 's that
reference the doc, you'll get valgrind errors like this:
==7390== Invalid read of size 4
==7390== at 0x4EB8BC6: xmlXPathFreeNodeSet (xpath.c:4185)
==7390== by 0x4EB8CC5: xmlXPathFreeObject (xpath.c:5492)
==7390== by 0x400A56: main (in /tmp/test)
==7390== Address 0x60c0928 is 8 bytes inside a block of size
2015 Jul 28
2
[PATCH] virtio_mmio: add ACPI probing
...'s call, I guess. I don't know enough about ACPI to say.
>> I thought these ACPI IDs were already fixed because they were
>> what the kernel was looking for...
> Apparently not :)
Mmm. I'm not terribly happy about stuff being in QEMU before the
ACPI spec for it has been finalised. We should not be picking
stuff randomly on the fly...
If we want to fix the ACPI IDs QEMU is using for 2.4 then we
really need to do that now (ie within the next day or two).
-- PMM
2015 Jul 28
2
[PATCH] virtio_mmio: add ACPI probing
...'s call, I guess. I don't know enough about ACPI to say.
>> I thought these ACPI IDs were already fixed because they were
>> what the kernel was looking for...
> Apparently not :)
Mmm. I'm not terribly happy about stuff being in QEMU before the
ACPI spec for it has been finalised. We should not be picking
stuff randomly on the fly...
If we want to fix the ACPI IDs QEMU is using for 2.4 then we
really need to do that now (ie within the next day or two).
-- PMM
2008 Oct 30
2
Inno setup script request
Dear all,
I am a public resaerch engineer in marseille (France) and I am currently developping a free software for high throughput experiments in biology using mainly R (bioconductor). This project is almost at a finalisation stage and I would like to build an installshield using innosetup for the windows version of my software. The ideal case would be to also include the required 2.6
2020 Jan 16
7
[RFC] Upstream development of support for yet-to-be-ratified RISC-V extensions
...fication, with a range of standard extensions (e.g. floating point,
atomics, etc). New standard extensions are developed through RISC-V
Foundation working groups. The specifications for such extensions (e.g. vector
and bit manipulation) are publicly available, but are still in flux and won't
be finalised until "ratified" by the Foundation. This RFC considers how we
should handle review and merging of support for in-development standard
extensions, with a view to maximising collaboration and reduce duplicate effort.
The summarised proposal is that patches for in-development standard
exten...
2012 Jun 16
2
Adding title to colorkey
...ist(layout.widths = list(axis.key.padding = 4)))
grid.text('title here', y=unit(0.5, "npc"),
rot=90, x=unit(0.88, "npc"))
i.e. adding some space between levelplot and colorkey. The
x,y positions of the grid.text call need fine-tuning once the plot is
close to finalised.
Does anyone have a better solution for vertical colorkeys? e.g. can the
plot objected be interrogated to work out what the central x,y value is?
Thanks, Stephen
2020 Oct 09
1
Aide pour finaliser ce code
Hello.
Here is my R code. I used the functional data . Now I need to use the
functional data by applying the kernels instead of the xi, yi functions.
Bonjour.
Voici mon code en R . J'ai utiliser les donn?es fonctionnelles . Maintenant
j'ai besoin d'utiliser les donn?es fonctionnelles en appliquant les noyaux
? la place des fontions xi, yi
library(MASS)
2006 Aug 30
5
Ready for real use?
...e
DirectShow filters release from February (which is quite dated now) it
seemed close to usable with the only critical bug being that it didn't
work under Windows 9x. As we are a commercial software producer we're a
bit nervous about using alpha software but if there is a chance it could
be finalised in the next year we'd be very interesting in using Theora.
Keep up the good work guys,
Doug
2020 Apr 23
1
volume control and setting volume on transfer
...ot; and the subsequent dial tone.
Is there a way that I can redefine "atxfer" in features.conf such that
the volume of the channel is set back to 1 before the transfer is made?
I would like to do the opposite after that, ie. return the volume of the
extension to 4 when the transfer is finalised with "atxferthreeway".
If anyone can help with this or has other suggestions, please let me know.
Thanks,
Iain
2020 Apr 15
0
[PATCH AUTOSEL 5.6 107/129] iommu/virtio: Fix freeing of incomplete domains
From: Jean-Philippe Brucker <jean-philippe at linaro.org>
[ Upstream commit 7062af3ed2ba451029e3733d9f677c68f5ea9e77 ]
Calling viommu_domain_free() on a domain that hasn't been finalised (not
attached to any device, for example) can currently cause an Oops,
because we attempt to call ida_free() on ID 0, which may either be
unallocated or used by another domain.
Only initialise the vdomain->viommu pointer, which denotes a finalised
domain, at the end of a successful viommu_domai...
2020 Apr 15
0
[PATCH AUTOSEL 5.5 088/106] iommu/virtio: Fix freeing of incomplete domains
From: Jean-Philippe Brucker <jean-philippe at linaro.org>
[ Upstream commit 7062af3ed2ba451029e3733d9f677c68f5ea9e77 ]
Calling viommu_domain_free() on a domain that hasn't been finalised (not
attached to any device, for example) can currently cause an Oops,
because we attempt to call ida_free() on ID 0, which may either be
unallocated or used by another domain.
Only initialise the vdomain->viommu pointer, which denotes a finalised
domain, at the end of a successful viommu_domai...
2020 Apr 15
0
[PATCH AUTOSEL 5.4 69/84] iommu/virtio: Fix freeing of incomplete domains
From: Jean-Philippe Brucker <jean-philippe at linaro.org>
[ Upstream commit 7062af3ed2ba451029e3733d9f677c68f5ea9e77 ]
Calling viommu_domain_free() on a domain that hasn't been finalised (not
attached to any device, for example) can currently cause an Oops,
because we attempt to call ida_free() on ID 0, which may either be
unallocated or used by another domain.
Only initialise the vdomain->viommu pointer, which denotes a finalised
domain, at the end of a successful viommu_domai...
2020 Apr 18
0
[PATCH AUTOSEL 5.6 48/73] iommu/virtio: Fix freeing of incomplete domains
From: Jean-Philippe Brucker <jean-philippe at linaro.org>
[ Upstream commit 7062af3ed2ba451029e3733d9f677c68f5ea9e77 ]
Calling viommu_domain_free() on a domain that hasn't been finalised (not
attached to any device, for example) can currently cause an Oops,
because we attempt to call ida_free() on ID 0, which may either be
unallocated or used by another domain.
Only initialise the vdomain->viommu pointer, which denotes a finalised
domain, at the end of a successful viommu_domai...
2020 Apr 18
0
[PATCH AUTOSEL 5.5 45/75] iommu/virtio: Fix freeing of incomplete domains
From: Jean-Philippe Brucker <jean-philippe at linaro.org>
[ Upstream commit 7062af3ed2ba451029e3733d9f677c68f5ea9e77 ]
Calling viommu_domain_free() on a domain that hasn't been finalised (not
attached to any device, for example) can currently cause an Oops,
because we attempt to call ida_free() on ID 0, which may either be
unallocated or used by another domain.
Only initialise the vdomain->viommu pointer, which denotes a finalised
domain, at the end of a successful viommu_domai...
2020 Apr 18
0
[PATCH AUTOSEL 5.4 42/78] iommu/virtio: Fix freeing of incomplete domains
From: Jean-Philippe Brucker <jean-philippe at linaro.org>
[ Upstream commit 7062af3ed2ba451029e3733d9f677c68f5ea9e77 ]
Calling viommu_domain_free() on a domain that hasn't been finalised (not
attached to any device, for example) can currently cause an Oops,
because we attempt to call ida_free() on ID 0, which may either be
unallocated or used by another domain.
Only initialise the vdomain->viommu pointer, which denotes a finalised
domain, at the end of a successful viommu_domai...
2007 Feb 13
2
language support
hi guys,
Just to touch base and restart the conversation about language support
in the wiki.
w.r.t the namespace / urlspace issue - did we finalise / decide on using
wiki.centos.org/<lang>/<namespace> ? or is that issue still open to
discussion ? Also, are pages in English going to remain as
wiki.centos.org/<namespace>/ ?
Also, iirc - someone was going to have a go at
2010 Mar 26
1
BaselR
...n Tues, Apr 27 at TransBARent:
http://transbarent.business.sv-group.ch
Doors open at 6:30,pm with the presentations starting at 7:00pm
Introduction: What is Basel R?
Andreas Krause:... Graphing Pharma Data
Yann Abraham: Graphics
Charles Roosen: Web based R reporting
(This agenda is yet to be finalised. We will notify any changes)
For further information or to register, please contact:
baselr@mango-solutions.com
Please also visit - www.mango-solutions.com and www.londonr.org
Sarah Lewis
mangosolutions
T: +44 (0)1249 767700
F: +44 (0)1249 767707
Unit 2 Greenways Business Park
Bellin...
2014 Jan 09
2
CentOS Tshirt ideas
hi,
We have, like in the years past, a table at Fosdem and I'd like to get
some tshirts printed to hand out. In the past, the Linux Ninja's and
Beards ones got quite a bit of attention ( and both were not brand
spammy, which is always nice ).
Reaching out to the mailing list for ideas on what we can do this year,
with the caveat that I need to finalise by this weekend if we are to get