linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Aurelien Thierry <aurelien.thierry@quoscient.io>
Cc: Arnd Bergmann <arnd@arndb.de>,
	John Stultz <john.stultz@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] Documentation: fix typo CLOCK_MONONOTNIC_COARSE
Date: Fri, 7 Jun 2019 11:22:33 -0600	[thread overview]
Message-ID: <20190607112233.1b91c3bb@lwn.net> (raw)
In-Reply-To: <593f6e44-af55-ac7c-1c67-12e515028fe5@quoscient.io>

On Fri, 7 Jun 2019 10:07:02 +0200
Aurelien Thierry <aurelien.thierry@quoscient.io> wrote:

> Fix typo in documentation file timekeeping.rst: CLOCK_MONONOTNIC_COARSE
> should be CLOCK_MONOTONIC_COARSE.
> 
> Signed-off-by: Aurelien Thierry <aurelien.thierry@quoscient.io>
> ---
>  Documentation/core-api/timekeeping.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/core-api/timekeeping.rst
> b/Documentation/core-api/timekeeping.rst
> index 93cbeb9daec0..5f87d9c8b04d 100644
> --- a/Documentation/core-api/timekeeping.rst
> +++ b/Documentation/core-api/timekeeping.rst
> @@ -111,7 +111,7 @@ Some additional variants exist for more specialized
> cases:
>          void ktime_get_coarse_raw_ts64( struct timespec64 * )
>  
>      These are quicker than the non-coarse versions, but less accurate,
> -    corresponding to CLOCK_MONONOTNIC_COARSE and CLOCK_REALTIME_COARSE
> +    corresponding to CLOCK_MONOTONIC_COARSE and CLOCK_REALTIME_COARSE
>      in user space, along with the equivalent boottime/tai/raw
>      timebase not available in user space.

Patch applied; congratulations on what appears to be your first kernel
patch!

Note that this patch was badly corrupted by your mailer; it took me a
while to unmangle it.  Before sending your next one, I'd recommend being
sure that you can email it to yourself and apply the result.  There are
some hints in Documentation/process/email-clients.rst.

Thanks,

jon

  reply	other threads:[~2019-06-07 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07  8:07 [PATCH] Documentation: fix typo CLOCK_MONONOTNIC_COARSE Aurelien Thierry
2019-06-07 17:22 ` Jonathan Corbet [this message]
2019-06-08  9:37   ` Aurelien Thierry

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=20190607112233.1b91c3bb@lwn.net \
    --to=corbet@lwn.net \
    --cc=arnd@arndb.de \
    --cc=aurelien.thierry@quoscient.io \
    --cc=john.stultz@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).