From: "Christian König" <christian.koenig@amd.com>
To: Daniel Vetter <daniel@ffwll.ch>, Randy Dunlap <rdunlap@infradead.org>
Cc: dri-devel@lists.freedesktop.org, patches@lists.linux.dev,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [Linaro-mm-sig] [PATCH] dma-buf/dma-resv: fix spelling
Date: Fri, 12 Jan 2024 15:32:51 +0100 [thread overview]
Message-ID: <54bf529d-c71b-4ee4-a025-bda48e6ac297@amd.com> (raw)
In-Reply-To: <ZaE4_l8PzXx9Isjp@phenom.ffwll.local>
Am 12.01.24 um 14:05 schrieb Daniel Vetter:
> On Wed, Jan 10, 2024 at 08:11:55PM -0800, Randy Dunlap wrote:
>> Fix spelling mistakes as reported by codespell.
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Sumit Semwal <sumit.semwal@linaro.org>
>> Cc: linux-media@vger.kernel.org
>> Cc: dri-devel@lists.freedesktop.org
>> Cc: Christian König <christian.koenig@amd.com>
>> Cc: linaro-mm-sig@lists.linaro.org
> Both dma-buf spell fixes applied to drm-misc-next, thanks!
Crap not fast enough. I was just about to reply that while at it we
could add in the other patch that GFP_ATOMIC or GFP_NOWAIT should be
sufficient.
But really just a minor addition.
Christian.
> -Sima
>> ---
>> drivers/dma-buf/dma-resv.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff -- a/drivers/dma-buf/dma-resv.c b/drivers/dma-buf/dma-resv.c
>> --- a/drivers/dma-buf/dma-resv.c
>> +++ b/drivers/dma-buf/dma-resv.c
>> @@ -405,7 +405,7 @@ static void dma_resv_iter_walk_unlocked(
>> *
>> * Beware that the iterator can be restarted. Code which accumulates statistics
>> * or similar needs to check for this with dma_resv_iter_is_restarted(). For
>> - * this reason prefer the locked dma_resv_iter_first() whenver possible.
>> + * this reason prefer the locked dma_resv_iter_first() whenever possible.
>> *
>> * Returns the first fence from an unlocked dma_resv obj.
>> */
>> @@ -428,7 +428,7 @@ EXPORT_SYMBOL(dma_resv_iter_first_unlock
>> *
>> * Beware that the iterator can be restarted. Code which accumulates statistics
>> * or similar needs to check for this with dma_resv_iter_is_restarted(). For
>> - * this reason prefer the locked dma_resv_iter_next() whenver possible.
>> + * this reason prefer the locked dma_resv_iter_next() whenever possible.
>> *
>> * Returns the next fence from an unlocked dma_resv obj.
>> */
>> _______________________________________________
>> Linaro-mm-sig mailing list -- linaro-mm-sig@lists.linaro.org
>> To unsubscribe send an email to linaro-mm-sig-leave@lists.linaro.org
prev parent reply other threads:[~2024-01-12 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 4:11 [PATCH] dma-buf/dma-resv: fix spelling Randy Dunlap
2024-01-12 13:05 ` [Linaro-mm-sig] " Daniel Vetter
2024-01-12 14:32 ` Christian König [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=54bf529d-c71b-4ee4-a025-bda48e6ac297@amd.com \
--to=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=sumit.semwal@linaro.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