Displaying 4 results from an estimated 4 matches for "mem_code".
Did you mean:
item_code
2016 Apr 04
0
[PATCH 2/2] Use 'error' function for fprintf followed by exit.
...ame);
- exit (EXIT_FAILURE);
- }
+ if (sscanf (p, "%d", &config->vcpus) != 1)
+ error (EXIT_FAILURE, 0,
+ "cannot parse p2v.vcpus from kernel command line");
}
p = get_cmdline_key (cmdline, "p2v.memory");
if (p) {
char mem_code;
- if (sscanf (p, "%" SCNu64 "%c", &config->memory, &mem_code) != 2) {
- fprintf (stderr, "%s: cannot parse p2v.memory from kernel command line\n",
- guestfs_int_program_name);
- exit (EXIT_FAILURE);
- }
+ if (sscanf (p, &q...
2018 Jun 29
3
p2v: Various cleanups.
These are a prelude to fixing
https://bugzilla.redhat.com/show_bug.cgi?id=1590220
A lot of the virt-p2v configuration code was duplicated manually.
These changes make sure that most of it is generated.
Rich.
2016 Apr 04
2
[PATCH 1/2] Use 'error' function consistently throughout.
Wherever we had code which did:
if (something_bad) {
perror (...);
exit (EXIT_FAILURE);
}
replace this with use of the error(3) function:
if (something_bad)
error (EXIT_FAILURE, errno, ...);
The error(3) function is supplied by glibc, or by gnulib on platforms
which don't have it, and is much more flexible than perror(3). Since
we already use error(3), there seems to be
2015 Feb 14
2
[PATCH 0/2] Change guestfs__*
libguestfs has used double and triple underscores in identifiers.
These aren't valid for global names in C++.
(http://stackoverflow.com/a/228797)
These large but completely mechanical patches change the illegal
identifiers to legal ones.
Rich.