mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Sebastian Fricke <sebastian.fricke@collabora.com>,
	linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>
Cc: kernel@collabora.com, bob.beckett@collabora.com,
	hverkuil-cisco@xs4all.nl, nicolas.dufresne@collabora.com,
	nas.chung@chipsnmedia.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v11 1/6] media: platform: chips-media: Move Coda to separate folder
Date: Wed, 07 Dec 2022 13:54:06 +0100	[thread overview]
Message-ID: <f3cd89a9d00918f222e3fe24c5512c7fb6bf1c0d.camel@pengutronix.de> (raw)
In-Reply-To: <20221207121350.66217-2-sebastian.fricke@collabora.com>

Hi Sebastian,

On Mi, 2022-12-07 at 13:13 +0100, Sebastian Fricke wrote:
> Prepare the folder structure for a second Chips&Media driver.
> Move the Coda driver to a sub-directory.
> 
> Signed-off-by: Sebastian Fricke <sebastian.fricke@collabora.com>
> ---
>  MAINTAINERS                                    |  2 +-
>  drivers/media/platform/chips-media/Kconfig     | 17 +----------------
>  drivers/media/platform/chips-media/Makefile    |  5 +----
>  .../media/platform/chips-media/coda/Kconfig    | 18 ++++++++++++++++++
>  .../media/platform/chips-media/coda/Makefile   |  6 ++++++
>  .../platform/chips-media/{ => coda}/coda-bit.c |  0
>  .../chips-media/{ => coda}/coda-common.c       |  0
>  .../platform/chips-media/{ => coda}/coda-gdi.c |  0
>  .../chips-media/{ => coda}/coda-h264.c         |  0
>  .../chips-media/{ => coda}/coda-jpeg.c         |  0
>  .../chips-media/{ => coda}/coda-mpeg2.c        |  0
>  .../chips-media/{ => coda}/coda-mpeg4.c        |  0
>  .../platform/chips-media/{ => coda}/coda.h     |  0
>  .../chips-media/{ => coda}/coda_regs.h         |  0
>  .../platform/chips-media/{ => coda}/imx-vdoa.c |  0
>  .../platform/chips-media/{ => coda}/imx-vdoa.h |  0
>  .../platform/chips-media/{ => coda}/trace.h    |  0

TRACE_INCLUDE_PATH in trace.h needs to be updated. For reference, see
commit 64441979bda6 ("media: platform: rename coda/ to chips-media/").

regards
Philipp

  reply	other threads:[~2022-12-07 12:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221207121350.66217-1-sebastian.fricke@collabora.com>
2022-12-07 12:13 ` Sebastian Fricke
2022-12-07 12:54   ` Philipp Zabel [this message]
2022-12-07 20:44   ` kernel test robot
2022-12-07 12:13 ` [PATCH v11 2/6] media: chips-media: wave5: Add vpuapi layer Sebastian Fricke
2022-12-07 13:05   ` AngeloGioacchino Del Regno
2022-12-15 13:31     ` Sebastian Fricke
2022-12-07 12:13 ` [PATCH v11 3/6] media: chips-media: wave5: Add the v4l2 layer Sebastian Fricke
2022-12-12 14:19   ` Hans Verkuil
2023-04-26 13:22     ` Nicolas Dufresne
2023-04-26 14:44   ` Nicolas Dufresne
2022-12-07 12:13 ` [PATCH v11 4/6] media: chips-media: wave5: Add TODO file Sebastian Fricke
2022-12-12 14:30   ` Hans Verkuil
2022-12-07 12:13 ` [PATCH v11 5/6] dt-bindings: media: wave5: add yaml devicetree bindings Sebastian Fricke
2022-12-07 12:31   ` Krzysztof Kozlowski
2022-12-07 13:17     ` Krzysztof Kozlowski
2022-12-07 15:09     ` Sebastian Fricke
2022-12-07 15:27       ` Krzysztof Kozlowski
2022-12-12 11:32         ` Sebastian Fricke
2023-09-04  6:25     ` Sebastian Fricke
2023-09-04  7:53       ` Krzysztof Kozlowski
2022-12-07 12:13 ` [PATCH v11 6/6] media: chips-media: wave5: Add wave5 driver to maintainers file Sebastian Fricke
2022-12-08  5:29   ` kernel test robot

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=f3cd89a9d00918f222e3fe24c5512c7fb6bf1c0d.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=bob.beckett@collabora.com \
    --cc=festevam@gmail.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=kernel@collabora.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nas.chung@chipsnmedia.com \
    --cc=nicolas.dufresne@collabora.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sebastian.fricke@collabora.com \
    --cc=shawnguo@kernel.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

all inboxes | Powered by JetHome®