From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Ricardo Ribalda <ribalda@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the v4l-dvb-next tree
Date: Mon, 9 May 2022 01:54:38 +0300 [thread overview]
Message-ID: <YnhKLsCyL66vigEI@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20220509082623.37c008f9@canb.auug.org.au>
Hi Stephen,
On Mon, May 09, 2022 at 08:26:23AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 18a9b21f7a9d ("media: uvcvideo: Fix memory leak if uvc_ctrl_add_mapping fails")
>
> Fixes tag
>
> Fixes: 07adedb5c606 ("media: uvcvideo: Use control names from framework")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 70fa906d6fce ("media: uvcvideo: Use control names from framework")
I've added a check to my git-request-pull wrapper for this, it won't
happen again.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-05-08 22:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 22:26 linux-next: Fixes tag needs some work in the v4l-dvb-next tree Stephen Rothwell
2022-05-08 22:54 ` Laurent Pinchart [this message]
-- 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-03-20 21:23 Stephen Rothwell
2023-03-20 21:50 ` Sakari Ailus
2023-02-06 21:08 Stephen Rothwell
2022-05-13 8:49 Stephen Rothwell
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=YnhKLsCyL66vigEI@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=sfr@canb.auug.org.au \
/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.