All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	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 tree
Date: Mon, 18 Jul 2022 08:25:27 +1000	[thread overview]
Message-ID: <20220718082527.18bfe5d5@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 364 bytes --]

Hi all,

In commit

  106be65a4119 ("media: mediatek: vcodec: decoder: Const-ify stepwise_fhd")

Fixes tag

  Fixes: ("76250b48de79 media: mediatek: vcodec: Getting supported decoder format types")

has these problem(s):

  - No SHA1 recognised

Please just use

  git log -1 --format='Fixes: %h ("%s")' <commit>

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-07-17 22:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17 22:25 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-17 22:29 linux-next: Fixes tag needs some work in the v4l-dvb tree 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-10-10 20:47 Stephen Rothwell
2019-10-11 12:28 ` Benoit Parrot
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=20220718082527.18bfe5d5@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=wenst@chromium.org \
    /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.