Re: [XEN PATCH 2/2] blkif: Fix a couple of typos

[Frediano Ziglio <frediano.ziglio@xxxxxxxxx>]

On Thu, Sep 26, 2024 at 1:54 PM Anthony PERARD
<anthony.perard@xxxxxxxxxx> wrote:
>
> Those where fixed in OVMF's copy. (And one of them fixed in QEMU's
> copy but later discarded by an update.)
>
> Signed-off-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
> ---
>  xen/include/public/io/blkif.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/xen/include/public/io/blkif.h b/xen/include/public/io/blkif.h
> index 789bab65ab..8407453324 100644
> --- a/xen/include/public/io/blkif.h
> +++ b/xen/include/public/io/blkif.h
> @@ -42,7 +42,7 @@
>   * All data in the XenStore is stored as strings.  Nodes specifying numeric
>   * values are encoded in decimal.  Integer value ranges listed below are
>   * expressed as fixed sized integer types capable of storing the conversion
> - * of a properly formated node string, without loss of information.
> + * of a properly formatted node string, without loss of information.
>   *
>   * Any specified default value is in effect if the corresponding XenBus node
>   * is not present in the XenStore.
> @@ -328,7 +328,7 @@
>   *      access (even when it should be read-only). If the frontend hits the
>   *      maximum number of allowed persistently mapped grants, it can fallback
>   *      to non persistent mode. This will cause a performance degradation,
> - *      since the the backend driver will still try to map those grants
> + *      since the backend driver will still try to map those grants
>   *      persistently. Since the persistent grants protocol is compatible with
>   *      the previous protocol, a frontend driver can choose to work in
>   *      persistent mode even when the backend doesn't support it.

Reviewed-by: Frediano Ziglio <frediano.ziglio@xxxxxxxxx>

Frediano