public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Masanari Iida <standby24x7@gmail.com>,
	mchehab@osg.samsung.com, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] [media] DocBook: Fix typo in intro.xml
Date: Fri, 24 Jul 2015 15:10:38 +0200	[thread overview]
Message-ID: <20150724151038.1b9e9981@lwn.net> (raw)
In-Reply-To: <55B1F86F.8010304@xs4all.nl>

On Fri, 24 Jul 2015 10:33:51 +0200
Hans Verkuil <hverkuil@xs4all.nl> wrote:

> Jon, would you mind if I take this patch and let it go through the media
> tree? I'd like to apply a patch on top of this one that removes the mention of
> devfs.

Fine, I'll drop it.

> It makes more sense in general to take patches to Documentation/DocBook/media
> via the media route.

OK.  I'll stick the following into MAINTAINERS so I'm not tempted to grab
them from you :)

jon

MAINTAINERS: Direct Documentation/DocBook/media properly

The media maintainers want DocBook changes to go through their tree;
document that wish accordingly.
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index b9b91566380e..11e2516c2712 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3440,6 +3440,7 @@ X:	Documentation/devicetree/
 X:	Documentation/acpi
 X:	Documentation/power
 X:	Documentation/spi
+X:	Documentation/DocBook/media
 T:	git git://git.lwn.net/linux-2.6.git docs-next
 
 DOUBLETALK DRIVER
-- 
2.4.3


  reply	other threads:[~2015-07-24 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 23:36 [PATCH] [media] DocBook: Fix typo in intro.xml Masanari Iida
2015-07-14 18:38 ` Jonathan Corbet
2015-07-24  8:33   ` Hans Verkuil
2015-07-24 13:10     ` Jonathan Corbet [this message]
2015-07-24 13:25       ` Hans Verkuil

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=20150724151038.1b9e9981@lwn.net \
    --to=corbet@lwn.net \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=standby24x7@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