From: "Wei, Jiangang" <weijg.fnst@cn.fujitsu.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"mark.d.rustad@intel.com" <mark.d.rustad@intel.com>,
"aik@ozlabs.ru" <aik@ozlabs.ru>
Subject: Re: [PATCH] vfio/pci: Fix typos in comments
Date: Wed, 24 Aug 2016 10:09:01 +0000 [thread overview]
Message-ID: <1472033331.7011.27.camel@localhost> (raw)
In-Reply-To: <1471415825-9231-1-git-send-email-weijg.fnst@cn.fujitsu.com>
ping...
On Wed, 2016-08-17 at 14:37 +0800, Wei Jiangang wrote:
> Signed-off-by: Wei Jiangang <weijg.fnst@cn.fujitsu.com>
> ---
> drivers/vfio/pci/vfio_pci_config.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/vfio/pci/vfio_pci_config.c b/drivers/vfio/pci/vfio_pci_config.c
> index 688691d9058d..c4f235452d81 100644
> --- a/drivers/vfio/pci/vfio_pci_config.c
> +++ b/drivers/vfio/pci/vfio_pci_config.c
> @@ -70,7 +70,7 @@ static const u8 pci_cap_length[PCI_CAP_ID_MAX + 1] = {
>
> /*
> * Lengths of PCIe/PCI-X Extended Config Capabilities
> - * 0: Removed or masked from the user visible capabilty list
> + * 0: Removed or masked from the user visible capability list
> * FF: Variable length
> */
> static const u16 pci_ext_cap_length[PCI_EXT_CAP_ID_MAX + 1] = {
> @@ -355,7 +355,7 @@ static int alloc_perm_bits(struct perm_bits *perm, int size)
> * ignore whether a read/write exceeds the defined capability
> * structure. We can do this because:
> * - Standard config space is already dword aligned
> - * - Capabilities are all dword alinged (bits 0:1 of next reserved)
> + * - Capabilities are all dword aligned (bits 0:1 of next reserved)
> * - Express capabilities defined as dword aligned
> */
> size = round_up(size, 4);
> @@ -1516,10 +1516,10 @@ static int vfio_ecap_init(struct vfio_pci_device *vdev)
> * space which tracks reads and writes to bits that we emulate for
> * the user. Initial values filled from device.
> *
> - * Using shared stuct perm_bits between all vfio-pci devices saves
> + * Using shared struct perm_bits between all vfio-pci devices saves
> * us from allocating cfg_size buffers for virt and write for every
> * device. We could remove vconfig and allocate individual buffers
> - * for each area requring emulated bits, but the array of pointers
> + * for each area requiring emulated bits, but the array of pointers
> * would be comparable in size (at least for standard config space).
> */
> int vfio_config_init(struct vfio_pci_device *vdev)
next prev parent reply other threads:[~2016-08-24 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 6:37 [PATCH] vfio/pci: Fix typos in comments Wei Jiangang
2016-08-24 10:09 ` Wei, Jiangang [this message]
2016-08-29 18:43 ` Alex Williamson
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=1472033331.7011.27.camel@localhost \
--to=weijg.fnst@cn.fujitsu.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.d.rustad@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox