All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-media@vger.kernel.org
Cc: Dan Scally <dan.scally@ideasonboard.com>
Subject: Re: [PATCH 1/1] MAINTAINERS: media: ipu-bridge: Add entry
Date: Tue, 11 Aug 2026 20:17:25 +0200	[thread overview]
Message-ID: <b1fb7dbc-0124-40ce-a988-445dcda7c000@kernel.org> (raw)
In-Reply-To: <20260811153822.396946-1-sakari.ailus@linux.intel.com>

Hi,

On 11-Aug-26 17:38, Sakari Ailus wrote:
> Add an entry for the ipu-bridge, a firmware parsing helper for the Intel
> IPU drivers, with myself and Dan Scally as maintainers and Hans de Goede
> as reviewer.
> 
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>

Thanks, patch looks good to me:

Acked-by: Hans de Goede <johannes.goede@oss.qualcomm.com>

Regards,

Hans



> ---
>  MAINTAINERS | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3785b8c1de0a..64fbdb8bc0b5 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -13142,6 +13142,15 @@ S:	Supported
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/iommu/linux.git
>  F:	drivers/iommu/intel/
>  
> +INTEL IPU BRIDGE
> +M:	Sakari Ailus <sakari.ailus@linux.intel.com>
> +M:	Dan Scally <dan.scally@ideasonboard.com>
> +R:	Hans de Goede <hansg@kernel.org>
> +L:	linux-media@vger.kernel.org
> +S:	Maintained
> +F:	drivers/media/pci/intel/ipu-bridge.c
> +F:	include/media/ipu-bridge.h
> +
>  INTEL IPU3 CSI-2 CIO2 DRIVER
>  M:	Yong Zhi <yong.zhi@intel.com>
>  M:	Sakari Ailus <sakari.ailus@linux.intel.com>


      reply	other threads:[~2026-08-11 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 15:38 [PATCH 1/1] MAINTAINERS: media: ipu-bridge: Add entry Sakari Ailus
2026-08-11 18:17 ` Hans de Goede [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=b1fb7dbc-0124-40ce-a988-445dcda7c000@kernel.org \
    --to=hansg@kernel.org \
    --cc=dan.scally@ideasonboard.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.