From: Benoit Parrot <bparrot@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Subject: Re: linux-next: Fixes tag needs some work in the v4l-dvb tree
Date: Fri, 11 Oct 2019 07:28:17 -0500 [thread overview]
Message-ID: <20191011122817.dlqlmayxlvghuphq@ti.com> (raw)
In-Reply-To: <20191011074702.1ebb98a7@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote on Fri [2019-Oct-11 07:47:02 +1100]:
> Hi all,
>
> In commit
>
> e20b248051ca ("media: ti-vpe: vpe: Make sure YUYV is set as default format")
>
> Fixes tag
>
> Fixes: 40cc823f7005 ("media: ti-vpe: Add support for NV21 format")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Did you mean
>
> Fixes: b2bb3d822f2c ("media: ti-vpe: Add support for NV21 format")
Ah, yes.
This was obviously missed through the rebase, sorry.
Benoit
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2019-10-11 12:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 20:47 linux-next: Fixes tag needs some work in the v4l-dvb tree Stephen Rothwell
2019-10-11 12:28 ` Benoit Parrot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-17 22:29 Stephen Rothwell
2022-07-17 22:25 Stephen Rothwell
2021-03-22 20:58 Stephen Rothwell
2020-11-17 8:04 Stephen Rothwell
2020-07-04 20:13 Stephen Rothwell
2020-05-20 11:52 Stephen Rothwell
2020-05-18 22:10 Stephen Rothwell
2020-02-27 21:06 Stephen Rothwell
2020-01-08 20:31 Stephen Rothwell
2019-06-22 13:47 Stephen Rothwell
2019-05-28 22:04 Stephen Rothwell
2019-05-29 21:05 ` Niklas Söderlund
2019-05-29 21:11 ` Mauro Carvalho Chehab
2019-04-22 21:22 Stephen Rothwell
2019-01-16 21:02 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=20191011122817.dlqlmayxlvghuphq@ti.com \
--to=bparrot@ti.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).