From: Liviu Dudau <liviu.dudau@arm.com>
To: Aryabhatta Dey <aryabhattadey35@gmail.com>
Cc: airlied@gmail.com, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, corbet@lwn.net,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/gpu: Fix typo in Documentation/gpu/komeda-kms.rst
Date: Tue, 27 Aug 2024 14:38:04 +0100 [thread overview]
Message-ID: <Zs3WvKCbvqCrIO0G@e110455-lin.cambridge.arm.com> (raw)
In-Reply-To: <l5wzytcamcc43eadaquqbrfqilq6ajfnnseh37c77eceamtw35@hhtdipi4h22c>
On Tue, Aug 27, 2024 at 06:48:52PM +0530, Aryabhatta Dey wrote:
> Change 'indenpendently' to 'independently'.
>
> Signed-off-by: Aryabhatta Dey <aryabhattadey35@gmail.com>
Acked-by: Liviu Dudau <liviu.dudau@arm.com>
Thanks for the patch!
Jonathan, is that something you can pick up in your tree?
Best regards,
Liviu
> ---
> Documentation/gpu/komeda-kms.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/gpu/komeda-kms.rst b/Documentation/gpu/komeda-kms.rst
> index 633a016563ae..eaea40eb725b 100644
> --- a/Documentation/gpu/komeda-kms.rst
> +++ b/Documentation/gpu/komeda-kms.rst
> @@ -86,7 +86,7 @@ types of working mode:
> - Single display mode
> Two pipelines work together to drive only one display output.
>
> - On this mode, pipeline_B doesn't work indenpendently, but outputs its
> + On this mode, pipeline_B doesn't work independently, but outputs its
> composition result into pipeline_A, and its pixel timing also derived from
> pipeline_A.timing_ctrlr. The pipeline_B works just like a "slave" of
> pipeline_A(master)
> --
> 2.46.0
>
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
next prev parent reply other threads:[~2024-08-27 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 13:18 Aryabhatta Dey
2024-08-27 13:38 ` Liviu Dudau [this message]
2024-09-05 20:33 ` Jonathan Corbet
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=Zs3WvKCbvqCrIO0G@e110455-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--cc=airlied@gmail.com \
--cc=aryabhattadey35@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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®