From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the v4l-dvb-next tree
Date: Thu, 5 Jan 2023 08:42:40 +1100 [thread overview]
Message-ID: <20230105084240.735cb1ce@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
Hi all,
The following commits already exist in Linus Torvald's tree as different
commits (but the same patches):
f523c655325c ("media: sun6i-csi: bridge: Error out on invalid port to fix warning")
6ceef05440ac ("media: sun6i-csi: capture: Remove useless ret initialization")
1607a95c0d81 ("media: sun6i-mipi-csi2: Clarify return code handling in stream off path")
73402fd7ac09 ("media: sun8i-a83t-mipi-csi2: Clarify return code handling in stream off path")
f7f346862bbc ("media: sun6i-isp: proc: Fix return code handling in stream off path")
5534ce51056d ("media: sun6i-isp: proc: Error out on invalid port to fix warning")
618001e8b1c6 ("media: sun6i-isp: proc: Declare subdev ops as static")
002886582094 ("media: sun6i-isp: capture: Fix uninitialized variable use")
10413ad08d57 ("media: sun6i-isp: params: Fix incorrect indentation")
d4acfa22b634 ("media: sun6i-isp: params: Unregister pending buffer on cleanup")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-01-04 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 21:42 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-04 22:26 linux-next: duplicate patches in the v4l-dvb-next tree Stephen Rothwell
2023-09-14 23:44 Stephen Rothwell
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=20230105084240.735cb1ce@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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