On Fri, Jun 08, 2018 at 07:38:17AM +0200, Thomas Huth wrote: > On 08.06.2018 00:31, Ross Zwisler wrote: > > Normally this might not be worth fixing, but several of these are strings > > which are displayed to users. > > > > Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com> > > --- > > hw/core/machine.c | 6 +++--- > > 1 file changed, 3 insertions(+), 3 deletions(-) > > > > diff --git a/hw/core/machine.c b/hw/core/machine.c > > index 617e5f8d75..a21269fa39 100644 > > --- a/hw/core/machine.c > > +++ b/hw/core/machine.c > > @@ -609,7 +609,7 @@ static void machine_class_init(ObjectClass *oc, void > > *data) > > machine_get_igd_gfx_passthru, machine_set_igd_gfx_passthru, > > &error_abort); > > object_class_property_set_description(oc, "igd-passthru", > > - "Set on/off to enable/disable igd passthrou", &error_abort); > > + "Set on/off to enable/disable igd passthru", &error_abort); > > Shouldn't that rather be "passthrough" instead?
Either works, I think. "thru" and "passthru" are short informal versions of "through" and "passthrough", but both the long and short versions of both words are used all over the QEMU source. "passthrou" is clearly wrong. If the longer version is preferred in this case please feel free to fix up when you apply. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
