diff options
author | Matthias Bolte <matthias.bolte@googlemail.com> | 2010-01-30 12:35:04 +0100 |
---|---|---|
committer | Matthias Bolte <matthias.bolte@googlemail.com> | 2010-02-04 19:09:28 +0100 |
commit | b1cd474c7726bbcd17faeb69e3a984a5d7af5e4b (patch) | |
tree | 2c49b82b4b734eeeec67a7f4bd86030d2a6c3582 /docs/hacking.html.in | |
parent | esx: Cleanup preprocessing structure in esxVI_EnsureSession (diff) | |
download | libvirt-b1cd474c7726bbcd17faeb69e3a984a5d7af5e4b.tar.gz libvirt-b1cd474c7726bbcd17faeb69e3a984a5d7af5e4b.tar.bz2 libvirt-b1cd474c7726bbcd17faeb69e3a984a5d7af5e4b.zip |
docs: Refer to virReportOOMError in the HACKING file
Instead of refering to __virRaiseError(VIR_ERROR_NO_MEMORY).
Diffstat (limited to 'docs/hacking.html.in')
-rw-r--r-- | docs/hacking.html.in | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/hacking.html.in b/docs/hacking.html.in index 96f6657cc..71b4f4714 100644 --- a/docs/hacking.html.in +++ b/docs/hacking.html.in @@ -192,8 +192,8 @@ virDomainPtr domain; if (VIR_ALLOC(domain) < 0) { - __virRaiseError(VIR_ERROR_NO_MEMORY) - return NULL; + virReportOOMError(NULL); + return NULL; } </pre></li> @@ -204,8 +204,8 @@ int ndomains = 10; if (VIR_ALLOC_N(domains, ndomains) < 0) { - __virRaiseError(VIR_ERROR_NO_MEMORY) - return NULL; + virReportOOMError(NULL); + return NULL; } </pre></li> @@ -216,8 +216,8 @@ int ndomains = 10; if (VIR_ALLOC_N(domains, ndomains) < 0) { - __virRaiseError(VIR_ERROR_NO_MEMORY) - return NULL; + virReportOOMError(NULL); + return NULL; } </pre></li> @@ -227,8 +227,8 @@ ndomains = 20 if (VIR_REALLOC_N(domains, ndomains) < 0) { - __virRaiseError(VIR_ERROR_NO_MEMORY) - return NULL; + virReportOOMError(NULL); + return NULL; } </pre></li> @@ -314,7 +314,7 @@ if (virBufferError(&buf)) { virBufferFreeAndReset(&buf); - virReportOOMError(...); + virReportOOMError(NULL); return NULL; } @@ -419,7 +419,7 @@ <li>if a recently commited patch breaks compilation on a platform or for a given driver then it's fine to commit a minimal fix directly without getting the review feedback first</li> - <li>if make check or make syntax-chek breaks, if there is + <li>if make check or make syntax-check breaks, if there is an obvious fix, it's fine to commit immediately. The patch should still be sent to the list (or tell what the fix was if trivial) and 'make check syntax-check' should pass too before commiting |