mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Abhash Jha <abhashkumarjha123@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	skhan@linuxfoundation.org
Subject: Re: [PATCH] LKMP(Bug fixing fall 2024): Fix documentation spelling errors
Date: Wed, 14 Aug 2024 11:44:20 +0100	[thread overview]
Message-ID: <20240814-vexingly-gigahertz-b4fca46f4626@spud> (raw)
In-Reply-To: <20240814103620.8912-1-abhashkumarjha123@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

On Wed, Aug 14, 2024 at 04:06:18PM +0530, Abhash Jha wrote:

btw, your commit $subject is rather odd, as it contains
"LKMP(Bug fixing fall 2024):".


>  Documentation/arch/riscv/vector.rst       | 2 +-
> --- a/Documentation/arch/riscv/vector.rst
> +++ b/Documentation/arch/riscv/vector.rst
> @@ -15,7 +15,7 @@ status for the use of Vector in userspace. The intended usage guideline for
>  these interfaces is to give init systems a way to modify the availability of V
>  for processes running under its domain. Calling these interfaces is not
>  recommended in libraries routines because libraries should not override policies
> -configured from the parant process. Also, users must noted that these interfaces
> +configured from the parent process. Also, users must noted that these interfaces
                                                        ^^^^^
						There's a second mistake
						in this line.


Cheers,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2024-08-14 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 10:36 Abhash Jha
2024-08-14 10:36 ` [PATCH] LKMP(Bug fixing fall 2024): Fix spelling mistakes in Documentation Abhash Jha
2024-08-14 10:44 ` Conor Dooley [this message]
2024-08-14 11:47   ` [PATCH] LKMP(Bug fixing fall 2024): Fix documentation spelling errors Abhash jha

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=20240814-vexingly-gigahertz-b4fca46f4626@spud \
    --to=conor@kernel.org \
    --cc=abhashkumarjha123@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.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

all inboxes | Powered by JetHome®