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>,
	Michael Rodin <mrodin@de.adit-jv.com>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>
Subject: linux-next: Fixes tag needs some work in the v4l-dvb-next tree
Date: Fri, 12 Jun 2020 07:17:15 +1000	[thread overview]
Message-ID: <20200612071715.4ae9ecf7@canb.auug.org.au> (raw)

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

Hi all,

In commit

  5be5f41dd785 ("media: v4l2-subdev.rst: correct information about v4l2 events")

Fixes tag

  Fixes: commit 02adb1cc765b ("[media] v4l: subdev: Events support")

has these problem(s):

  - leading word 'commit' unexpected

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-06-11 21:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 21:17 Stephen Rothwell [this message]
2021-05-23  2:49 linux-next: Fixes tag needs some work in the v4l-dvb-next tree Stephen Rothwell
2021-05-23  8:36 ` Sean Young
2021-05-23  9:30   ` Mauro Carvalho Chehab
2021-06-17 10:54 Stephen Rothwell
2021-07-22 22:51 Stephen Rothwell
2021-07-23  0:38 ` Yizhuo Zhai
2021-07-23  0:58   ` Stephen Rothwell
2021-07-23  2:19     ` Yizhuo Zhai
2021-07-23  7:04   ` Mauro Carvalho Chehab
2021-10-18 20:40 Stephen Rothwell
2021-12-06  9:06 Stephen Rothwell
2021-12-06  9:27 ` Mauro Carvalho Chehab
2022-05-08 22:26 Stephen Rothwell
2022-05-08 22:54 ` Laurent Pinchart
2022-05-13  8:49 Stephen Rothwell
2023-02-06 21:08 Stephen Rothwell
2023-03-20 21:23 Stephen Rothwell
2023-03-20 21:50 ` Sakari Ailus
2023-07-16 21:53 Stephen Rothwell
2023-07-30 21:55 Stephen Rothwell
2023-07-31 22:29 ` Sakari Ailus

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=20200612071715.4ae9ecf7@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=mrodin@de.adit-jv.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.