From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-pci@vger.kernel.org, Linas Vepstas <linasvepstas@gmail.com>
Subject: [PATCH 4/4] Documentation: PCI: pci.rst: drop doubled words
Date: Fri, 3 Jul 2020 14:21:56 -0700 [thread overview]
Message-ID: <20200703212156.30453-5-rdunlap@infradead.org> (raw)
In-Reply-To: <20200703212156.30453-1-rdunlap@infradead.org>
Drop the doubled word "when".
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org
---
Documentation/PCI/pci.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20200701.orig/Documentation/PCI/pci.rst
+++ linux-next-20200701/Documentation/PCI/pci.rst
@@ -209,7 +209,7 @@ the PCI device by calling pci_enable_dev
OS BUG: we don't check resource allocations before enabling those
resources. The sequence would make more sense if we called
pci_request_resources() before calling pci_enable_device().
- Currently, the device drivers can't detect the bug when when two
+ Currently, the device drivers can't detect the bug when two
devices have been allocated the same range. This is not a common
problem and unlikely to get fixed soon.
next prev parent reply other threads:[~2020-07-03 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 21:21 [PATCH 0/4] Documentation: PCI: eliminate doubled words Randy Dunlap
2020-07-03 21:21 ` [PATCH 1/4] Documentation: PCI: pci-endpoint-cfs: drop " Randy Dunlap
2020-07-03 21:21 ` [PATCH 2/4] Documentation: PCI: pci-endpoint: " Randy Dunlap
2020-07-03 21:21 ` [PATCH 3/4] Documentation: PCI: pci-error-recovery: " Randy Dunlap
2020-07-04 6:08 ` Linas Vepstas
2020-07-03 21:21 ` Randy Dunlap [this message]
2020-07-05 11:49 ` [PATCH 0/4] Documentation: PCI: eliminate " Mike Rapoport
2020-07-05 20:40 ` Jonathan Corbet
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=20200703212156.30453-5-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=kishon@ti.com \
--cc=linasvepstas@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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 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.