From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, Bingbu Cao <bingbu.cao@intel.com>
Subject: Re: [PATCH v3 0/5] media: intel/ipu6: continue on ipu7 code sharing preparation
Date: Fri, 9 May 2025 06:25:00 +0200 [thread overview]
Message-ID: <aB2DnGn39pSKcZh8@linux.intel.com> (raw)
In-Reply-To: <aBhzDoUZSb40MzBv@kekkonen.localdomain>
Hi Sakari,
On Mon, May 05, 2025 at 08:13:02AM +0000, Sakari Ailus wrote:
> Hi Stanislaw,
>
> On Fri, May 02, 2025 at 05:44:41PM +0200, Stanislaw Gruszka wrote:
> > Cleanups and code sharing preparation with ipu7 driver.
> >
> > This is on top of:
> > https://git.linuxtv.org/sailus/media_tree.git/log/?h=devel
> > Plus:
> > https://lore.kernel.org/linux-media/20250317073856.162147-1-stanislaw.gruszka@linux.intel.com/
> > https://lore.kernel.org/linux-media/20250428161643.321617-1-stanislaw.gruszka@linux.intel.com/#t
>
> Thanks for these. I've applied patches from 1 to 3 for now.
>
> Going forward, could you post cleanups and reorganising the code into
> common bits in separate sets?
I don't know what can be cleaned up before I start modifying the code.
And since I change a lot of code during refactoring, changing patches order
and separate the changes is not that easy, I would prefer to do this.
> It'll be easier to see where this is going
> when all related patches are in the same set. Cleanups and fixes we can
> merge earlier on anyway.
I can post bigger sets.
Regards
Stanislaw
prev parent reply other threads:[~2025-05-09 4:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 15:44 [PATCH v3 0/5] media: intel/ipu6: continue on ipu7 code sharing preparation Stanislaw Gruszka
2025-05-02 15:44 ` [PATCH v3 1/5] media: intel/ipu6: Remove pin_ready function pointer Stanislaw Gruszka
2025-05-02 15:44 ` [PATCH v3 2/5] media: intel/ipu6: Remove line_align Stanislaw Gruszka
2025-05-02 15:44 ` [PATCH v3 3/5] media: intel/ipu6: Change deprecated lock comment Stanislaw Gruszka
2025-05-02 15:44 ` [PATCH v3 4/5] media: intel/ipu6: Move common structures definitions to ipu-isys.h Stanislaw Gruszka
2025-05-02 15:44 ` [PATCH v3 5/5] media: intel/ipu6: Rename common structures Stanislaw Gruszka
2025-05-05 8:13 ` [PATCH v3 0/5] media: intel/ipu6: continue on ipu7 code sharing preparation Sakari Ailus
2025-05-09 4:25 ` Stanislaw Gruszka [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=aB2DnGn39pSKcZh8@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=linux-media@vger.kernel.org \
--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