From: Dan Carpenter <dan.carpenter@linaro.org>
To: Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>
Cc: hansg@kernel.org, mchehab@kernel.org,
sakari.ailus@linux.intel.com, andy@kernel.org,
gregkh@linuxfoundation.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org
Subject: Re: [PATCH 0/3] staging: media: atomisp: More Cleanup on driver AtomIsp
Date: Wed, 16 Jul 2025 21:21:44 +0300 [thread overview]
Message-ID: <eb7fd8f3-1d6e-421f-b5d9-f9e2d2992da5@suswa.mountain> (raw)
In-Reply-To: <20250712191325.132666-1-abdelrahmanfekry375@gmail.com>
On Sat, Jul 12, 2025 at 10:13:22PM +0300, Abdelrahman Fekry wrote:
> Continuing the cleanup work that is being done on the AtomIsp driver,
> This series:
>
> - Process the error inside hmm_init().
> - Unifies the HMM init tracking method.
> - move hmm related function to hmm.c.
>
> Previously, These patches were sent individualy but they build on
> each other so i resent them as one patch series
>
> Suggested-by: Hans de Goede <hansg@kernel.org>
> Signed-off-by: Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>
These seem reasonable enough to me.
Reviewed-by: Dan Carpenter <dan.carpenter@linaro.org>
But it would be better if someone could test them as well.
regards,
dan carpenter
next prev parent reply other threads:[~2025-07-16 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-12 19:13 Abdelrahman Fekry
2025-07-12 19:13 ` [PATCH 1/3] staging: media: atomisp: return early on hmm_bo_device_init() failure Abdelrahman Fekry
2025-07-12 19:13 ` [PATCH 2/3] staging: media: atomisp: unify HMM initialization tracking Abdelrahman Fekry
2025-07-12 19:13 ` [PATCH 3/3] staging: media: atomisp: move hmm_get_mmu_base_addr() Abdelrahman Fekry
2025-07-16 18:21 ` Dan Carpenter [this message]
2025-07-17 1:35 ` [PATCH 0/3] staging: media: atomisp: More Cleanup on driver AtomIsp Abdelrahman Fekry
2025-07-31 3:24 ` Abdelrahman Fekry
2025-07-31 4:35 ` Greg KH
2025-07-31 5:59 ` Abdelrahman Fekry
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=eb7fd8f3-1d6e-421f-b5d9-f9e2d2992da5@suswa.mountain \
--to=dan.carpenter@linaro.org \
--cc=abdelrahmanfekry375@gmail.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®