From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the v4l-dvb-next tree
Date: Tue, 21 Mar 2023 08:23:44 +1100 [thread overview]
Message-ID: <20230321082344.6250cfc6@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 346 bytes --]
Hi all,
In commit
71937240a472 ("media: ov2685: Select VIDEO_V4L2_SUBDEV_API")
Fixes tag
Fixes: ("media: i2c: ov2685: Add .get_selection() support")
has these problem(s):
- No SHA1 recognised
Maybe you meant
Fixes: 859128ab6f0f ("media: i2c: ov2685: Add .get_selection() support")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-03-20 21:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 21:23 Stephen Rothwell [this message]
2023-03-20 21:50 ` linux-next: Fixes tag needs some work in the v4l-dvb-next tree Sakari Ailus
-- strict thread matches above, loose matches on Subject: below --
2023-07-30 21:55 Stephen Rothwell
2023-07-31 22:29 ` Sakari Ailus
2023-07-16 21:53 Stephen Rothwell
2023-02-06 21:08 Stephen Rothwell
2022-05-13 8:49 Stephen Rothwell
2022-05-08 22:26 Stephen Rothwell
2022-05-08 22:54 ` Laurent Pinchart
2021-12-06 9:06 Stephen Rothwell
2021-12-06 9:27 ` Mauro Carvalho Chehab
2021-10-18 20:40 Stephen Rothwell
2021-07-22 22:51 Stephen Rothwell
2021-07-23 0:38 ` Yizhuo Zhai
2021-07-23 0:58 ` Stephen Rothwell
2021-07-23 2:19 ` Yizhuo Zhai
2021-07-23 7:04 ` Mauro Carvalho Chehab
2021-06-17 10:54 Stephen Rothwell
2021-05-23 2:49 Stephen Rothwell
2021-05-23 8:36 ` Sean Young
2021-05-23 9:30 ` Mauro Carvalho Chehab
2020-06-11 21:17 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=20230321082344.6250cfc6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@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.