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 0/7] media: intel/ipu6: continue on ipu7 code sharing preparation
Date: Mon, 14 Apr 2025 12:11:58 +0200 [thread overview]
Message-ID: <Z/zfbpSmzCDOW9mo@linux.intel.com> (raw)
In-Reply-To: <Z_fk_ofTOzsvbRwZ@kekkonen.localdomain>
On Thu, Apr 10, 2025 at 03:34:22PM +0000, Sakari Ailus wrote:
> Hi Stanislaw,
>
> On Mon, Apr 07, 2025 at 03:40:30PM +0200, Stanislaw Gruszka wrote:
> > Move and rename more structures to isys.h. Add accessors to make
> > further transformation easier.
> >
> > 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/20250401090953.473339-1-stanislaw.gruszka@linux.intel.com/
> >
> > Stanislaw Gruszka (7):
> > media: intel/ipu6: Use isd name in isys.h
> > media: intel/ipu6: Remove line_align
> > media: intel/ipu6: Move common structures definitions to isys.h
> > media: intel/ipu6: Rename common structures
> > media: intel/ipu6: Remove deprecated lock comment
> > media: intel/ipu6: Introduce isys and dev accessors macros
> > media: intel/ipu6: Start using accessors to get dev pointer
>
> My main comment to the set is naming. Can we do so that we keep the current
> scheme (ipu or ipu-isys prefix, with or without IPU generation number) and
> then reconsider this question when the result (hopefully including IPU 7
> ISYS support) is in upstream?
Ok, I'll use ipu_isys_ prefix for functions, structures and some macros.
However for some macros I think it would make sense to skip ipu prefix to
make the names shorter.
Regards
Stanislaw
> The rest seems entirely reasonable to me -- but see my other comments, too.
>
> --
> Kind regards,
>
> Sakari Ailus
next prev parent reply other threads:[~2025-04-14 10:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 13:40 [PATCH 0/7] media: intel/ipu6: continue on ipu7 code sharing preparation Stanislaw Gruszka
2025-04-07 13:40 ` [PATCH 1/7] media: intel/ipu6: Use isd name in isys.h Stanislaw Gruszka
2025-04-07 13:40 ` [PATCH 2/7] media: intel/ipu6: Remove line_align Stanislaw Gruszka
2025-04-10 12:04 ` Sakari Ailus
2025-04-10 13:12 ` Stanislaw Gruszka
2025-04-10 15:34 ` Sakari Ailus
2025-04-07 13:40 ` [PATCH 3/7] media: intel/ipu6: Move common structures definitions to isys.h Stanislaw Gruszka
2025-04-07 13:40 ` [PATCH 4/7] media: intel/ipu6: Rename common structures Stanislaw Gruszka
2025-04-07 13:40 ` [PATCH 5/7] media: intel/ipu6: Remove deprecated lock comment Stanislaw Gruszka
2025-04-07 13:40 ` [PATCH 6/7] media: intel/ipu6: Introduce isys and dev accessors macros Stanislaw Gruszka
2025-04-07 13:40 ` [PATCH 7/7] media: intel/ipu6: Start using accessors to get dev pointer Stanislaw Gruszka
2025-04-10 15:34 ` [PATCH 0/7] media: intel/ipu6: continue on ipu7 code sharing preparation Sakari Ailus
2025-04-14 10:11 ` Stanislaw Gruszka [this message]
2025-04-14 12:52 ` Sakari Ailus
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=Z/zfbpSmzCDOW9mo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.