From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Anushka B <anushkabadhe@gmail.com>
Cc: andriy.shevchenko@intel.com, andy@kernel.org,
gregkh@linuxfoundation.org, hansg@kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev, mchehab@kernel.org,
Daniel Baluta <daniel.baluta@nxp.com>,
Dhruva gole <goledhruva@gmail.com>,
m-chawdhry@ti.com, Simona Toaca <simona.toaca@nxp.com>
Subject: Re: [PATCH v6] staging: media: atomisp: fix GP_TIMER_BASE scope in gp_timer.c
Date: Wed, 1 Apr 2026 09:55:07 +0300 [thread overview]
Message-ID: <aczBS_KJQa_j97RP@kekkonen.localdomain> (raw)
In-Reply-To: <CAAfE=nNNxCKv0JoRcib7YVQfQ9MxqE34WyYu2GHNYaroxzpw1w@mail.gmail.com>
Hi Anushka,
On Mon, Mar 30, 2026 at 07:02:21AM +0530, Anushka B wrote:
> > There's a lot to cleanup here, but what should be done is roughly:
> >
> > - Make these constants macros (with IPU2_ or ATOMISP2_ prefix?) and move
> > them into a separate header (perhaps with register definitions?).
> >
> > - Remove my_env and make struct device (or maybe struct atomisp_device?) as
> > a parameter for register access functions.
> >
> > This may get a bit complicated due to the amount of cleanup needed so
> > having the hardware for testing would be rather essential.
> As a student, I don't currently have access to the hardware needed to
> do the bigger refactor safely. However I'm happy to fix the comment
> formatting and language.
> In earlier versions, I had merged the split declaration of
> GP_TIMER_BASE in place in system_local.c before later moving it to
> gp_timer.c.
> Link: https://lore.kernel.org/linux-media/20260325132434.55775-1-anushkabadhe@gmail.com/
> Would it be okay to proceed with the simpler in-place fix for
> GP_TIMER_BASE declaration instead?
I'm fine with v4.
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-04-01 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 3:11 [PATCH v6] staging: media: atomisp: fix GP_TIMER_BASE scope in gp_timer.c Anushka Badhe
2026-03-27 9:43 ` Andy Shevchenko
2026-03-30 1:19 ` Anushka B
2026-03-30 8:47 ` Andy Shevchenko
2026-03-27 11:24 ` Sakari Ailus
2026-03-30 1:32 ` Anushka B
2026-04-01 6:55 ` Sakari Ailus [this message]
2026-04-01 16:02 ` Anushka B
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=aczBS_KJQa_j97RP@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=anushkabadhe@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=goledhruva@gmail.com \
--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=m-chawdhry@ti.com \
--cc=mchehab@kernel.org \
--cc=simona.toaca@nxp.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