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>,
	"Ezequiel Garcia" <ezequiel@collabora.com>,
	"Lucas A. M. Magalhães" <lucmaga@gmail.com>
Subject: linux-next: Fixes tags need some work in the v4l-dvb tree
Date: Fri, 8 Feb 2019 07:39:43 +1100	[thread overview]
Message-ID: <20190208073943.0317d5ea@canb.auug.org.au> (raw)

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

Hi Mauro,

In commit

  c2d88e7d66f9 ("media: vb2: Fix buf_out_validate documentation")

Fixes tag

  Fixes: 28d77c21cb ("media: vb2: add buf_out_validate callback")

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").

In commit

  adc589d2a208 ("media: vimc: Add vimc-streamer for stream control")

Fixes tag

  Fixes: f2fe89061d797 ("vimc: Virtual Media Controller core, capture

has these problem(s):

  - Subject has leading but no trailing parentheses
  - Subject has leading but no trailing quotes
  - Subject does not match target commit subject

Please do not split Fixes tags over more than one line.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-02-07 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 20:39 Stephen Rothwell [this message]
2019-03-19 21:21 linux-next: Fixes tags need some work in the v4l-dvb tree Stephen Rothwell
2019-05-08 21:53 Stephen Rothwell
2020-05-06 18:57 Stephen Rothwell
2021-11-22 21:24 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=20190208073943.0317d5ea@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ezequiel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lucmaga@gmail.com \
    --cc=mchehab@kernel.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 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).