mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: 岳秉坤 <yuebingkun@kylinos.cn>, mchehab@kernel.org
Cc: jacopo.mondi@ideasonboard.com, laurent.pinchart@ideasonboard.com,
	hverkuil+cisco@kernel.org, sakari.ailus@linux.intel.com,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: fix a few typo and wording issues
Date: Mon, 27 Jul 2026 20:23:05 -0700	[thread overview]
Message-ID: <c571b85e-e202-46fc-b3be-792b3a105fb9@infradead.org> (raw)
In-Reply-To: <20260728030748.45399-1-yuebingkun@kylinos.cn>

Hi,

On 7/27/26 8:07 PM, 岳秉坤 wrote:
> Hi,
> 
> This patch fixes a few small documentation issues in Documentation/ files.

These changes look good to me. Thanks.
Acked-by: Randy Dunlap <rdunlap@infradead.org>

> I am a newcomer to the Linux community, and I am eager to contribute
> and learn through small, helpful fixes like this one.
> 
However, there are probably some process issues here.

E.g., the 2 lines above should not be part of the commit message. You can
include them after the "---" line just after your Signed-off-by: line.

> These changes are limited to spelling and wording corrections and do not
> change behavior.
> 
> Signed-off-by: 岳秉坤 <yuebingkun@kylinos.cn>
> ---
>  Documentation/ABI/README                                        | 2 +-
>  Documentation/ABI/testing/sysfs-edac-memory-repair              | 2 +-
>  .../userspace-api/media/v4l/vidioc-subdev-g-routing.rst         | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 

and it's up to various maintainers as to whether the patch will have to be
split up into multiple patches to be applied.

> diff --git a/Documentation/ABI/README b/Documentation/ABI/README
> index 315fffe1f831f..27c962e6a872c 100644
> --- a/Documentation/ABI/README
> +++ b/Documentation/ABI/README
> @@ -62,7 +62,7 @@ Users:		All users of this interface who wish to be notified when
>  
>  
>  Note:
> -   The fields should be use a simple notation, compatible with ReST markup.
> +   The fields should use a simple notation, compatible with ReST markup.
>     Also, the file **should not** have a top-level index, like::
>  
>  	===
> diff --git a/Documentation/ABI/testing/sysfs-edac-memory-repair b/Documentation/ABI/testing/sysfs-edac-memory-repair
> index 0434a3b23ff3e..ab199132ffd8a 100644
> --- a/Documentation/ABI/testing/sysfs-edac-memory-repair
> +++ b/Documentation/ABI/testing/sysfs-edac-memory-repair
> @@ -160,7 +160,7 @@ Description:
>  		in trace events, such as CXL DRAM and CXL general media
>  		error records of CXL memory devices.
>  
> -		When readng back these attributes, it returns the current
> +		When reading back these attributes, it returns the current
>  		value of memory requested to be repaired.
>  
>  		bank_group - The bank group of the memory to repair.
> diff --git a/Documentation/userspace-api/media/v4l/vidioc-subdev-g-routing.rst b/Documentation/userspace-api/media/v4l/vidioc-subdev-g-routing.rst
> index 6f66ca38589e8..164cf0ad35931 100644
> --- a/Documentation/userspace-api/media/v4l/vidioc-subdev-g-routing.rst
> +++ b/Documentation/userspace-api/media/v4l/vidioc-subdev-g-routing.rst
> @@ -67,7 +67,7 @@ subdevice routing table. This may be smaller or larger than the value of
>  drivers may adjust the requested routing table.
>  
>  The kernel can return a ``num_routes`` value larger than ``len_routes`` from
> -both ioctls. This indicates thare are more routes in the routing table than fits
> +both ioctls. This indicates there are more routes in the routing table than fits
>  the ``routes`` array. In this case, the ``routes`` array is filled by the kernel
>  with the first ``len_routes`` entries of the subdevice routing table. This is
>  not considered to be an error, and the ioctl call succeeds. If the applications

-- 
~Randy

  reply	other threads:[~2026-07-28  3:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  3:07 岳秉坤
2026-07-28  3:23 ` Randy Dunlap [this message]
2026-07-28  7:55 ` Sakari Ailus
2026-07-28  8:16   ` 岳秉坤

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=c571b85e-e202-46fc-b3be-792b3a105fb9@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=hverkuil+cisco@kernel.org \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=yuebingkun@kylinos.cn \
    /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®