All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Changyuan Lyu <changyuanl@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	kvm@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/3] Documentation: Fix typo `BFD`
Date: Fri, 28 Jun 2024 21:57:52 +0000	[thread overview]
Message-ID: <Zn8x4Fxr6JFq37Nw@linux.dev> (raw)
In-Reply-To: <20240623164542.2999626-1-changyuanl@google.com>

Hi Changyuan,

Thanks for the fixes. LGTM, but next time you have a multi-patch series
please include a cover letter. Helps with organizing the patch series
on the receiving end :)

On Sun, Jun 23, 2024 at 09:45:39AM -0700, Changyuan Lyu wrote:
> BDF is the acronym for Bus, Device, Function.
> 
> Signed-off-by: Changyuan Lyu <changyuanl@google.com>
> ---
>  Documentation/virt/kvm/api.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index a71d91978d9ef..e623f072e9aca 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -1921,7 +1921,7 @@ flags:
>  
>  If KVM_MSI_VALID_DEVID is set, devid contains a unique device identifier
>  for the device that wrote the MSI message.  For PCI, this is usually a
> -BFD identifier in the lower 16 bits.
> +BDF identifier in the lower 16 bits.
>  
>  On x86, address_hi is ignored unless the KVM_X2APIC_API_USE_32BIT_IDS
>  feature of KVM_CAP_X2APIC_API capability is enabled.  If it is enabled,
> @@ -2986,7 +2986,7 @@ flags:
>  
>  If KVM_MSI_VALID_DEVID is set, devid contains a unique device identifier
>  for the device that wrote the MSI message.  For PCI, this is usually a
> -BFD identifier in the lower 16 bits.
> +BDF identifier in the lower 16 bits.
>  
>  On x86, address_hi is ignored unless the KVM_X2APIC_API_USE_32BIT_IDS
>  feature of KVM_CAP_X2APIC_API capability is enabled.  If it is enabled,
> -- 
> 2.45.2.741.gdbec12cfda-goog
> 

-- 
Thanks,
Oliver

  parent reply	other threads:[~2024-06-28 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23 16:45 [PATCH 1/3] Documentation: Fix typo `BFD` Changyuan Lyu
2024-06-23 16:45 ` [PATCH 2/3] Documentation: Enumerate allowed value macros of `irq_type` Changyuan Lyu
2024-06-23 16:45 ` [PATCH 3/3] Documentation: Correct the VGIC V2 CPU interface addr space size Changyuan Lyu
2024-06-28 21:57 ` Oliver Upton [this message]
2024-06-28 22:11 ` [PATCH 1/3] Documentation: Fix typo `BFD` Oliver Upton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zn8x4Fxr6JFq37Nw@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=changyuanl@google.com \
    --cc=corbet@lwn.net \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.