From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Prabhav Kumar Vaish <pvkumar5749404@gmail.com>,
mike.leach@linaro.org, james.clark@arm.com
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Correcting the spelling mistakes in "Documentation/ABI/testing/sysfs-bus-cxl" and "Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc"
Date: Mon, 26 Feb 2024 15:55:30 +0000 [thread overview]
Message-ID: <02138784-d9fd-4331-bb34-fe1bd2fd043f@arm.com> (raw)
In-Reply-To: <20240220214212.10231-1-pvkumar5749404@gmail.com>
Hi Prabhav,
On 20/02/2024 21:42, Prabhav Kumar Vaish wrote:
Thanks for sending the patch. Please find some comments.
> Signed-off-by: Prabhav Kumar Vaish <pvkumar5749404@gmail.com>
Only one "Signed-off-by:" tag is required, the second one below
is at the desired location. So, please drop the above.
>
> Changes:
> - "avaialble" corrected to "available" in "Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc"
> - "firwmare" corrected to "firmware" in "Documentation/ABI/testing/sysfs-bus-cxl"
It is advisable to split this patch into two, as they affect files
maintained by different subsystems. i.e., coresight and CXL. Since
they go via different maintainers, it is always better to split
the patch (especially when there is no functional dependency, like
this case).
Also, I see that you haven't copied any of the maintainers for the CXL
subsystem. Running "scripts/get_maintainer.pl" on the affected file
or the patch should give you the email addresses for the concerned
maintainers/list.
e.g:
$ scripts/get_maintainer.pl Documentation/ABI/testing/sysfs-bus-cxl
So, please resend the patch after splitting, to the respective
maintainers/reviewers/list.
Suzuki
> Signed-off-by: Prabhav Kumar Vaish <pvkumar5749404@gmail.com>
> ---
> Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc | 2 +-
> Documentation/ABI/testing/sysfs-bus-cxl | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc b/Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc
> index 96aafa66b4a5..339cec3b2f1a 100644
> --- a/Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc
> +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc
> @@ -97,7 +97,7 @@ Date: August 2023
> KernelVersion: 6.7
> Contact: Anshuman Khandual <anshuman.khandual@arm.com>
> Description: (Read) Shows all supported Coresight TMC-ETR buffer modes available
> - for the users to configure explicitly. This file is avaialble only
> + for the users to configure explicitly. This file is available only
> for TMC ETR devices.
>
> What: /sys/bus/coresight/devices/<memory_map>.tmc/buf_mode_preferred
> diff --git a/Documentation/ABI/testing/sysfs-bus-cxl b/Documentation/ABI/testing/sysfs-bus-cxl
> index fff2581b8033..bbf6de5a4ca1 100644
> --- a/Documentation/ABI/testing/sysfs-bus-cxl
> +++ b/Documentation/ABI/testing/sysfs-bus-cxl
> @@ -224,7 +224,7 @@ Description:
> decoding a Host Physical Address range. Note that this number
> may be elevated without any regionX objects active or even
> enumerated, as this may be due to decoders established by
> - platform firwmare or a previous kernel (kexec).
> + platform firmware or a previous kernel (kexec).
>
>
> What: /sys/bus/cxl/devices/decoderX.Y
next prev parent reply other threads:[~2024-02-26 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 21:42 [PATCH] Correcting the spelling mistakes in "Documentation/ABI/testing/sysfs-bus-cxl" and "Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc" Prabhav Kumar Vaish
2024-02-26 15:55 ` Suzuki K Poulose [this message]
[not found] ` <CAH8oh8W5=sAw8Lf6n_LRtxqdLde-+F2NeMTTc1SJSSpQNasFnA@mail.gmail.com>
2024-02-27 11:17 ` Suzuki K Poulose
[not found] ` <CAH8oh8XcHGL_jdwLJJKa3qW0xQ6D36_LEUXFJUkzhdVNygSGjQ@mail.gmail.com>
2024-02-26 17:12 ` Suzuki K Poulose
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=02138784-d9fd-4331-bb34-fe1bd2fd043f@arm.com \
--to=suzuki.poulose@arm.com \
--cc=james.clark@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=pvkumar5749404@gmail.com \
/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