From: Jonathan Corbet <corbet@lwn.net>
To: Mark-PK Tsai <mark-pk.tsai@mediatek.com>, bagasdotme@gmail.com
Cc: Brian.Starkey@arm.com, benjamin.gaignard@collabora.com,
christian.koenig@amd.com, dri-devel@lists.freedesktop.org,
jstultz@google.com, labbott@redhat.com,
linaro-mm-sig@lists.linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-mediatek@lists.infradead.org, lmark@codeaurora.org,
mark-pk.tsai@mediatek.com, matthias.bgg@gmail.com,
sumit.semwal@linaro.org, yj.chiang@mediatek.com
Subject: Re: [PATCH v2] dma-buf: cma_heap: Fix typo in comment
Date: Fri, 28 Oct 2022 08:47:33 -0600 [thread overview]
Message-ID: <87k04k6m4a.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221028065907.23954-1-mark-pk.tsai@mediatek.com>
Mark-PK Tsai <mark-pk.tsai@mediatek.com> writes:
>> [-- Attachment #1: Type: text/plain, Size: 349 bytes --]
>>
>> On Fri, Oct 28, 2022 at 09:44:17AM +0800, Mark-PK Tsai wrote:
>> > Remove duplicated "by" from comment in cma_heap_allocate().
>> >
>>
>> This patch isn't typofix but duplicate word stripping, right? If so, the
>> patch subject should be "dma-buf: cma_heap: Remove duplicated 'by'".
>
> Okay, I've update the title in v3.
> Sorry for the horrible commit description.
> Thanks.
Your original commit description was just fine, you just had the bad
luck to draw the attention of somebody who likes telling other
contributors what to do.
Thanks,
jon
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-10-28 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 1:44 [PATCH v2] dma-buf: cma_heap: Fix typo in comment Mark-PK Tsai
2022-10-28 3:54 ` Bagas Sanjaya
2022-10-28 6:59 ` Mark-PK Tsai
2022-10-28 14:47 ` Jonathan Corbet [this message]
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=87k04k6m4a.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=Brian.Starkey@arm.com \
--cc=bagasdotme@gmail.com \
--cc=benjamin.gaignard@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jstultz@google.com \
--cc=labbott@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lmark@codeaurora.org \
--cc=mark-pk.tsai@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=yj.chiang@mediatek.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;
as well as URLs for NNTP newsgroup(s).