All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/10] iio: documentation: fix a typo
Date: Thu, 20 May 2021 21:08:16 +0100	[thread overview]
Message-ID: <YKbBsOnQyThisWDP@casper.infradead.org> (raw)
In-Reply-To: <ebe6c6597409fb9748e6c05d8e8cb3bd3fa4c6f4.1621413933.git.mchehab+huawei@kernel.org>

On Wed, May 19, 2021 at 10:51:47AM +0200, Mauro Carvalho Chehab wrote:
> @@ -798,7 +798,7 @@ What:		/sys/.../in_capacitanceY_adaptive_thresh_rising_timeout
>  What:		/sys/.../in_capacitanceY_adaptive_thresh_falling_timeout
>  KernelVersion:	5.11
>  Contact:	linux-iio@vger.kernel.org
> -Descrption:
> +Description:
>  		When adaptive thresholds are used, the tracking signal
>  		may adjust too slowly to step changes in the raw signal.
>  		*_timeout (in seconds) specifies a time for which the

This must be the warning Jon refers to.  * as wildcard, rather than
* as emphasis marker.

  reply	other threads:[~2021-05-20 20:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  8:51 [PATCH 00/10] Documentation build warning fixes Mauro Carvalho Chehab
2021-05-19  8:51 ` Mauro Carvalho Chehab
2021-05-19  8:51 ` Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 01/10] docs: update sysfs-platform_profile.rst reference Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 02/10] docs: vcpu-requests.rst: fix reference for atomic ops Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 03/10] docs: translations/zh_CN: fix a typo at 8.Conclusion.rst Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 04/10] docs: sched-bwc.rst: fix a typo on a doc name Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 05/10] docs: update pin-control.rst references Mauro Carvalho Chehab
2021-05-19  8:51   ` Mauro Carvalho Chehab
2021-05-19 10:20   ` Charles Keepax
2021-05-19 10:20     ` Charles Keepax
2021-05-19 14:43   ` Lee Jones
2021-05-19 14:43     ` Lee Jones
2021-05-25  0:30   ` Linus Walleij
2021-05-25  0:30     ` Linus Walleij
2021-05-19  8:51 ` [PATCH 06/10] docs: virt: api.rst: fix a pointer to SGX documentation Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 07/10] docs: ABI: iommu: remove duplicated definition for sysfs-kernel-iommu_groups Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 08/10] docs: ABI: sysfs-class-backlight: unify ambient light zone nodes Mauro Carvalho Chehab
2021-05-19  8:51   ` Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 09/10] docs: ABI: sysfs-class-led-trigger-pattern: remove repeat duplication Mauro Carvalho Chehab
2021-05-19  8:51 ` [PATCH 10/10] iio: documentation: fix a typo Mauro Carvalho Chehab
2021-05-20 20:08   ` Matthew Wilcox [this message]
2021-05-20 20:00 ` [PATCH 00/10] Documentation build warning fixes Jonathan Corbet
2021-05-20 20:00   ` Jonathan Corbet
2021-05-20 20:00   ` 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=YKbBsOnQyThisWDP@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=corbet@lwn.net \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@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.