From: Dan Carpenter <dan.carpenter@linaro.org>
To: Mohammed EL Kadiri <med08elkadiri@gmail.com>
Cc: hansg@kernel.org, mchehab@kernel.org, gregkh@linuxfoundation.org,
andy@kernel.org, sakari.ailus@linux.intel.com,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@intel.com>
Subject: Re: [PATCH v3] media: atomisp: fix spelling mistake
Date: Mon, 23 Mar 2026 19:01:55 +0300 [thread overview]
Message-ID: <acFj89pWfmhLKzQ4@stanley.mountain> (raw)
In-Reply-To: <20260323141143.27280-1-med08elkadiri@gmail.com>
On Mon, Mar 23, 2026 at 03:11:43PM +0100, Mohammed EL Kadiri wrote:
> diff --git a/drivers/staging/media/atomisp/pci/hmm/hmm_bo.c b/drivers/staging/media/atomisp/pci/hmm/hmm_bo.c
> index 856561e951a5..a6eab5f52b75 100644
> --- a/drivers/staging/media/atomisp/pci/hmm/hmm_bo.c
> +++ b/drivers/staging/media/atomisp/pci/hmm/hmm_bo.c
> @@ -434,7 +434,7 @@ void hmm_bo_release(struct hmm_buffer_object *bo)
> /*
> * FIX ME:
> *
> - * how to destroy the bo when it is stilled MMAPED?
> + * how to destroy the bo when it is stilled MAPPED?
MMAPPED was correct. It means memory mapped.
> *
> * ideally, this will not happened as hmm_bo_release
> * will only be called when kref reaches 0, and in mmap
> @@ -443,7 +443,7 @@ void hmm_bo_release(struct hmm_buffer_object *bo)
> */
> if (bo->status & HMM_BO_MMAPED) {
> mutex_unlock(&bdev->rbtree_mutex);
> - dev_dbg(atomisp_dev, "destroy bo which is MMAPED, do nothing\n");
> + dev_dbg(atomisp_dev, "destroy bo which is MAPPED, do nothing\n");
Same.
> return;
> }
>
(always wait a day between resending a patch in case other people have
feedback).
regards,
dan carpenter
next prev parent reply other threads:[~2026-03-23 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 14:11 [PATCH v3] media: atomisp: fix spelling mistake Mohammed EL Kadiri
2026-03-23 16:01 ` Dan Carpenter [this message]
2026-03-23 16:45 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2026-03-23 14:17 Mohammed EL Kadiri
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=acFj89pWfmhLKzQ4@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=med08elkadiri@gmail.com \
--cc=sakari.ailus@linux.intel.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