public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>
To: hansg@kernel.org, mchehab@kernel.org,
	sakari.ailus@linux.intel.org, andy@kernel.org,
	gregkh@linuxfoundation.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev,
	linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
	dan.carpenter@linaro.org,
	Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>
Subject: [PATCH 0/2] staging: media: atomisp: clean up and unify HMM initialization logic
Date: Mon,  7 Jul 2025 17:09:21 +0300	[thread overview]
Message-ID: <20250707140923.58935-1-abdelrahmanfekry375@gmail.com> (raw)

Continuing the series of cleaning up the atomisp driver as discussed in
[1], This patch series improves the consistency and reliability of the
initialization logic in the AtomISP driver's Hybrid Memory Manager (HMM)
subsystem.

These modifications were tested by building the AtomISP driver

Link: https://lore.kernel.org/all/fbfbd0e5-2c27-4f32-a3d7-9cf57fde5098@kernel.org/ [1]
Abdelrahman Fekry (2):
  staging: media: atomisp: return early on hmm_bo_device_init() failure
  staging: media: atomisp: unify initialization flag usage in HMM

 .../media/atomisp/include/hmm/hmm_bo.h        |  9 +++++++--
 drivers/staging/media/atomisp/pci/hmm/hmm.c   | 19 ++++++-------------
 2 files changed, 13 insertions(+), 15 deletions(-)

-- 
2.25.1


             reply	other threads:[~2025-07-07 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 14:09 Abdelrahman Fekry [this message]
2025-07-07 14:09 ` [PATCH 1/2] staging: media: atomisp: return early on hmm_bo_device_init() failure Abdelrahman Fekry
2025-07-07 14:12   ` Hans de Goede
2025-07-07 14:15     ` Abdelrahman Fekry
2025-07-14 19:13       ` Dan Carpenter
2025-07-14 20:11         ` Abdelrahman Fekry
2025-07-07 14:09 ` [PATCH 2/2] staging: media: atomisp: unify initialization flag usage in HMM Abdelrahman Fekry
2025-07-07 14:14   ` Hans de Goede
2025-07-07 15:01     ` Hans de Goede
2025-07-08 14:54     ` 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=20250707140923.58935-1-abdelrahmanfekry375@gmail.com \
    --to=abdelrahmanfekry375@gmail.com \
    --cc=andy@kernel.org \
    --cc=dan.carpenter@linaro.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.org \
    --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