[PATCH] Documentation: fix typo CLOCK_MONONOTNIC_COARSE

[PATCH] Documentation: fix typo CLOCK_MONONOTNIC_COARSE

[Aurelien Thierry]

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.
 
-- 
2.17.1

Re: [PATCH] Documentation: fix typo CLOCK_MONONOTNIC_COARSE

[Jonathan Corbet]

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

Re: [PATCH] Documentation: fix typo CLOCK_MONONOTNIC_COARSE

[Aurelien Thierry]

It is indeed my first kernel patch, I'll definitely make sure that I
can apply the patch next time.
Thank you!

Aurelien


On 6/7/19 7:22 PM, Jonathan Corbet wrote:
> 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
>