[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v1] Remove stale crashkernel= example from documentation
Am Wed, 4 Sep 2019 14:19:23 +0200 schrieb Jan Beulich <jbeulich@xxxxxxxx>: > On 04.09.2019 11:37, Olaf Hering wrote: > > Maybe just the lack of b49225dc9df336405292dc08862b4c7c9d887bd6 in vendor > > binaries... > But this change was only to deal with the bogus log message. > The handling was still correct (and the option was being > honored). I also can't see how this would be different now. Is that true? My interpretation of the code path is that no colon and nothing after a size value will lead to EINVAL. With this change any unknown string will cause EINVAL. Olaf Attachment:
pgpur5VcTrTNF.pgp _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |