From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org,
Media Submaintainers <media-submaintainers@linuxtv.org>
Subject: Re: [media-submaintainers] [GIT FIXES FOR 6.4 v2] V4L2 fixes for 6.4
Date: Thu, 18 May 2023 09:45:41 +0100 [thread overview]
Message-ID: <20230518094541.03d3dc9c@sal.lan> (raw)
In-Reply-To: <ZGTPurnmJ4KQfjrr@valkosipuli.retiisi.eu>
Em Wed, 17 May 2023 15:59:38 +0300
Sakari Ailus <sakari.ailus@iki.fi> escreveu:
> Hi Mauro,
>
> This set includes fixes for 6.4.
>
> Please pull.
>
>
> The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
>
> Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
>
> are available in the Git repository at:
>
> git://linuxtv.org/sailus/media_tree.git tags/fixes-6.4-2.1-signed
>
> for you to fetch changes up to a9b5a8a05f0143a48c7bf1d06e9f62bf5e0fdde0:
>
> staging: media: imx: initialize hs_settle to avoid warning (2023-05-17 15:57:07 +0300)
>
> ----------------------------------------------------------------
> V4L2 fixes for 6.4
>
> ----------------------------------------------------------------
> Hans Verkuil (1):
> staging: media: imx: initialize hs_settle to avoid warning
Applied, thanks!
>
> Tomi Valkeinen (1):
> media: v4l2-subdev: Fix missing kerneldoc for client_caps
This one has an issue, as it will add a new Sphinx warning by adding
a word ending with an asterisk.
So, not applied.
>
> Vaishnav Achath (1):
> media: v4l2-mc: Drop subdev check in v4l2_create_fwnode_links_to_pad()
Applied, thanks!
Regards,
Mauro
prev parent reply other threads:[~2023-05-18 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 12:59 [GIT FIXES FOR 6.4 v2] V4L2 fixes for 6.4 Sakari Ailus
2023-05-17 13:20 ` [GIT FIXES FOR 6.4 v2] V4L2 fixes for 6.4 (#91898) Jenkins
2023-05-18 8:45 ` Mauro Carvalho Chehab [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=20230518094541.03d3dc9c@sal.lan \
--to=mchehab@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=media-submaintainers@linuxtv.org \
--cc=sakari.ailus@iki.fi \
/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.