linux-next.vger.kernel.org archive mirror
 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>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Steve Longerbeam <slongerbeam@gmail.com>
Subject: linux-next: Fixes tags need some work in the v4l-dvb tree
Date: Wed, 20 Mar 2019 08:21:03 +1100	[thread overview]
Message-ID: <20190320082103.33faecc9@canb.auug.org.au> (raw)

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

Hi all,

In commit

  e6f8bd59c28f ("media: gspca: do not resubmit URBs when streaming has stopped")

Fixes tag

  Fixes: 6992effe5344 ("gspca: Kill all URBs before releasing any of them")

has these problem(s):

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

In commit

  904371f90b2c ("media: imx: csi: Allow unknown nearest upstream entities")

Fixes tag

  Fixes: bf3cfaa712e5c ("media: staging/imx: get CSI bus type from nearest

has these problem(s):

  - Subject has leading but no trailing parentheses
  - Subject has leading but no trailing quotes

Please do not wrap Fixes tags onto more that one line.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-03-19 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 21:21 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-22 21:24 linux-next: Fixes tags need some work in the v4l-dvb tree Stephen Rothwell
2020-05-06 18:57 Stephen Rothwell
2019-05-08 21:53 Stephen Rothwell
2019-02-07 20:39 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=20190320082103.33faecc9@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=slongerbeam@gmail.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 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).