From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D53D8C5519F for ; Wed, 18 Nov 2020 07:46:48 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id EEA1622228 for ; Wed, 18 Nov 2020 07:46:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="B7w1pf/R" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EEA1622228 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:59932 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kfIAw-00034j-Io for qemu-devel@archiver.kernel.org; Wed, 18 Nov 2020 02:46:46 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:41600) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfI9F-0002Gw-8T for qemu-devel@nongnu.org; Wed, 18 Nov 2020 02:45:02 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:43673) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from ) id 1kfI9B-0007BL-AJ for qemu-devel@nongnu.org; Wed, 18 Nov 2020 02:44:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1605685496; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Cr60BNQVpl2Jv0xMsNMxK646YXoW+AI1Myjdlseyb9Q=; b=B7w1pf/RE9/SciEeQ83463gFa2JA4VAMWDoPpZySR13/9Tg71Zpt1f2QSOoOre2GiXtbSa lWois2maR8aV2IsY3Gw/jtajON0iRCY10MfQN62PhuVTh3MiwFP7ljFCD8CJ6wXWiM1Dnw TBVVDfWKUqoviB2k12jiJGy0MYEPSS0= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-172-nxlFtsxNOS6wbmWuNOa6Vw-1; Wed, 18 Nov 2020 02:44:52 -0500 X-MC-Unique: nxlFtsxNOS6wbmWuNOa6Vw-1 Received: by mail-wm1-f69.google.com with SMTP id 3so662643wms.9 for ; Tue, 17 Nov 2020 23:44:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Cr60BNQVpl2Jv0xMsNMxK646YXoW+AI1Myjdlseyb9Q=; b=IVM7Llvn96eDw9AunixBDeohd3cK0QTOKrdiKyqBt4QHJP5K8tKq+FdxqZNJl4Jr+v v7VHrshxRYup+r7uS11RZLYUjEXSMaZsirFWAG1YETFvKod7RH+ZqGjNpZZctkj6GobB 00EDu3S+MFIV/JbOl0txcSTANo6jyp8HMv6jPK+3vpwosrlLqKrnB9D6pXSsi/oRdI60 JDzJxiE+xGFHkOujKP5Zgl1ywIdeRcn8yXI4ZhXzhhHnbOoiH76fhf8bOfN2q8eAwxq7 eU2PHIDANuUvh9/hvzS5wCKpLGATIDKbeJjgctEXbIDXs3VGqy/8jFzVGm3OSd8FoaF+ 01jA== X-Gm-Message-State: AOAM532PBbAxSFbyyiq+UdKuUtV8BNRN5Pi00wSM9ML9612GWP8vMwbh LsbQiHChUKDlEg54inpCROOi+IG/awmHn6r+KXtWCW4diGWqq92lejAumdwPQwQxb+u0uFzlNkM Lm77ru9jI8q2DCzM= X-Received: by 2002:a05:600c:2202:: with SMTP id z2mr3068946wml.95.1605685491522; Tue, 17 Nov 2020 23:44:51 -0800 (PST) X-Google-Smtp-Source: ABdhPJwrp6OVOpaidqfArBZtHWZIw0GmdCT5r4RKOQu2MGAiH5e8B5jciqpMWcNYRyWSI9py6rKZQg== X-Received: by 2002:a05:600c:2202:: with SMTP id z2mr3068917wml.95.1605685491232; Tue, 17 Nov 2020 23:44:51 -0800 (PST) Received: from redhat.com (bzq-79-176-118-93.red.bezeqint.net. [79.176.118.93]) by smtp.gmail.com with ESMTPSA id 109sm32971104wra.29.2020.11.17.23.44.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Nov 2020 23:44:50 -0800 (PST) Date: Wed, 18 Nov 2020 02:44:45 -0500 From: "Michael S. Tsirkin" To: Stefan Weil Subject: Re: [PATCH for-5.2] docs: Fix some typos (found by codespell) Message-ID: <20201118024440-mutt-send-email-mst@kernel.org> References: <20201117193448.393472-1-sw@weilnetz.de> MIME-Version: 1.0 In-Reply-To: <20201117193448.393472-1-sw@weilnetz.de> Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mst@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Received-SPF: pass client-ip=63.128.21.124; envelope-from=mst@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/17 19:41:43 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org, libvir-list@redhat.com, Alex Williamson , Pavel Dovgalyuk , Paolo Bonzini Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Tue, Nov 17, 2020 at 08:34:48PM +0100, Stefan Weil wrote: > Fix also a similar typo in a code comment. > > Signed-off-by: Stefan Weil Reviewed-by: Michael S. Tsirkin > --- > docs/can.txt | 8 ++++---- > docs/interop/vhost-user.rst | 2 +- > docs/replay.txt | 2 +- > docs/specs/ppc-spapr-numa.rst | 2 +- > docs/system/deprecated.rst | 4 ++-- > docs/tools/virtiofsd.rst | 2 +- > hw/vfio/igd.c | 2 +- > 7 files changed, 11 insertions(+), 11 deletions(-) > > diff --git a/docs/can.txt b/docs/can.txt > index 5838f6620c..0d310237df 100644 > --- a/docs/can.txt > +++ b/docs/can.txt > @@ -19,7 +19,7 @@ interface to implement because such device can be easily connected > to systems with different CPU architectures (x86, PowerPC, Arm, etc.). > > In 2020, CTU CAN FD controller model has been added as part > -of the bachelor theses of Jan Charvat. This controller is complete > +of the bachelor thesis of Jan Charvat. This controller is complete > open-source/design/hardware solution. The core designer > of the project is Ondrej Ille, the financial support has been > provided by CTU, and more companies including Volkswagen subsidiaries. > @@ -31,7 +31,7 @@ testing lead to goal change to provide environment which provides complete > emulated environment for testing and RTEMS GSoC slot has been donated > to work on CAN hardware emulation on QEMU. > > -Examples how to use CAN emulation for SJA1000 based borads > +Examples how to use CAN emulation for SJA1000 based boards > ========================================================== > > When QEMU with CAN PCI support is compiled then one of the next > @@ -106,8 +106,8 @@ This open-source core provides CAN FD support. CAN FD drames are > delivered even to the host systems when SocketCAN interface is found > CAN FD capable. > > -The PCIe borad emulation is provided for now (the device identifier is > -ctucan_pci). The defauld build defines two CTU CAN FD cores > +The PCIe board emulation is provided for now (the device identifier is > +ctucan_pci). The default build defines two CTU CAN FD cores > on the board. > > Example how to connect the canbus0-bus (virtual wire) to the host > diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-user.rst > index 988f154144..72b2e8c7ba 100644 > --- a/docs/interop/vhost-user.rst > +++ b/docs/interop/vhost-user.rst > @@ -513,7 +513,7 @@ descriptor table (split virtqueue) or descriptor ring (packed > virtqueue). However, it can't work when we process descriptors > out-of-order because some entries which store the information of > inflight descriptors in available ring (split virtqueue) or descriptor > -ring (packed virtqueue) might be overrided by new entries. To solve > +ring (packed virtqueue) might be overridden by new entries. To solve > this problem, slave need to allocate an extra buffer to store this > information of inflight descriptors and share it with master for > persistent. ``VHOST_USER_GET_INFLIGHT_FD`` and > diff --git a/docs/replay.txt b/docs/replay.txt > index 87a64ae068..5b008ca491 100644 > --- a/docs/replay.txt > +++ b/docs/replay.txt > @@ -328,7 +328,7 @@ between the snapshots. Each of the passes include the following steps: > 1. loading the snapshot > 2. replaying to examine the breakpoints > 3. if breakpoint or watchpoint was met > - - loading the snaphot again > + - loading the snapshot again > - replaying to the required breakpoint > 4. else > - proceeding to the p.1 with the earlier snapshot > diff --git a/docs/specs/ppc-spapr-numa.rst b/docs/specs/ppc-spapr-numa.rst > index 5fca2bdd8e..ffa687dc89 100644 > --- a/docs/specs/ppc-spapr-numa.rst > +++ b/docs/specs/ppc-spapr-numa.rst > @@ -198,7 +198,7 @@ This is how it is being done: > * user distance 121 and beyond will be interpreted as 160 > * user distance 10 stays 10 > > -The reasoning behind this aproximation is to avoid any round up to the local > +The reasoning behind this approximation is to avoid any round up to the local > distance (10), keeping it exclusive to the 4th NUMA level (which is still > exclusive to the node_id). All other ranges were chosen under the developer > discretion of what would be (somewhat) sensible considering the user input. > diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst > index 32a0e620db..63e9db1463 100644 > --- a/docs/system/deprecated.rst > +++ b/docs/system/deprecated.rst > @@ -465,7 +465,7 @@ default configuration. > > The CPU model runnability guarantee won't apply anymore to > existing CPU models. Management software that needs runnability > -guarantees must resolve the CPU model aliases using te > +guarantees must resolve the CPU model aliases using the > ``alias-of`` field returned by the ``query-cpu-definitions`` QMP > command. > > @@ -637,7 +637,7 @@ Splitting RAM by default between NUMA nodes had the same issues as ``mem`` > parameter with the difference that the role of the user plays QEMU using > implicit generic or board specific splitting rule. > Use ``memdev`` with *memory-backend-ram* backend or ``mem`` (if > -it's supported by used machine type) to define mapping explictly instead. > +it's supported by used machine type) to define mapping explicitly instead. > Users of existing VMs, wishing to preserve the same RAM distribution, should > configure it explicitly using ``-numa node,memdev`` options. Current RAM > distribution can be retrieved using HMP command ``info numa`` and if separate > diff --git a/docs/tools/virtiofsd.rst b/docs/tools/virtiofsd.rst > index 34a9e40146..866b7db3ee 100644 > --- a/docs/tools/virtiofsd.rst > +++ b/docs/tools/virtiofsd.rst > @@ -174,7 +174,7 @@ Using ':' as the separator a rule is of the form: > - 'bad' - If a client tries to use a name matching 'key' it's > denied using EPERM; when the server passes an attribute > name matching 'prepend' it's hidden. In many ways it's use is very like > - 'ok' as either an explict terminator or for special handling of certain > + 'ok' as either an explicit terminator or for special handling of certain > patterns. > > **key** is a string tested as a prefix on an attribute name originating > diff --git a/hw/vfio/igd.c b/hw/vfio/igd.c > index 64e332746b..470205f487 100644 > --- a/hw/vfio/igd.c > +++ b/hw/vfio/igd.c > @@ -535,7 +535,7 @@ void vfio_probe_igd_bar4_quirk(VFIOPCIDevice *vdev, int nr) > } > > /* > - * Assume we have no GMS memory, but allow it to be overrided by device > + * Assume we have no GMS memory, but allow it to be overridden by device > * option (experimental). The spec doesn't actually allow zero GMS when > * when IVD (IGD VGA Disable) is clear, but the claim is that it's unused, > * so let's not waste VM memory for it. > -- > 2.29.2