mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: Anushka B <anushkabadhe@gmail.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
	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: Thu, 16 Apr 2026 14:22:29 +0300	[thread overview]
Message-ID: <aeDGdRKoE_7FNSJw@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <CAAfE=nOs9YfpnFGY+bPg1WPxuCHOzkR9oHD9DizNxxse25A0hw@mail.gmail.com>

Hi Anushka,

On Wed, Apr 01, 2026 at 09:32:29PM +0530, Anushka B wrote:
> > > Would it be okay to proceed with the simpler in-place fix for
> > > GP_TIMER_BASE declaration instead?
> >
> > I'm fine with v4.
> 
> Should I send a v7 similar to v4, where I merged the split declaration
> of GP_TIMER_BASE, and a separate patch for the comment fixes?

Yes, please.

You can find the currently applied patches in my atomisp branch here:
<URL:https://git.linuxtv.org/sailus/media_tree.git/log/?h=atomisp>.

-- 
Regards,

Sakari Ailus

      reply	other threads:[~2026-04-16 11:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27  3:11 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
2026-04-01 16:02       ` Anushka B
2026-04-16 11:22         ` Sakari Ailus [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=aeDGdRKoE_7FNSJw@valkosipuli.retiisi.eu \
    --to=sakari.ailus@iki.fi \
    --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=sakari.ailus@linux.intel.com \
    --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

all inboxes | Powered by JetHome®