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: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: linux-next: Fixes tag needs some work in the v4l-dvb tree
Date: Fri, 28 Feb 2020 08:06:12 +1100	[thread overview]
Message-ID: <20200228080612.1858eb8b@canb.auug.org.au> (raw)

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

Hi all,

In commit

  ab07b1a6ac6e ("media: omap3isp: Prevent enabling CCDC when stopping streaming")

Fixes tag

  Fixes: dd12ed17ce9e ("omap3isp: Don't restart CCDC if we're about to stop")

has these problem(s):

  - Subject does not match target commit subject
    Just use
	git log -1 --format='Fixes: %h ("%s")'

Also, please keep all the commit message tags together at the end of
the commit message.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-02-27 21:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 21:06 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
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-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=20200228080612.1858eb8b@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.