linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: "linux-media" <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: RFC: First draft of guidelines for submitting patches to linux-media
Date: Tue, 11 Dec 2012 14:15:31 +0100	[thread overview]
Message-ID: <201212111415.31483.hverkuil@xs4all.nl> (raw)
In-Reply-To: <201212101407.09338.hverkuil@xs4all.nl>

On Mon 10 December 2012 14:07:09 Hans Verkuil wrote:
> Hi all,
> 
> As discussed in Barcelona I would write a text describing requirements for new
> drivers and what to expect when submitting patches to linux-media.
> 
> This is a first rough draft and nothing is fixed yet.
> 
> I have a few open questions:
> 
> 1) Where to put it? One thing I would propose that we improve is to move the
> dvb and video4linux directories in Documentation/ to Documentation/media to
> correctly reflect the drivers/media structure. If we do that, then we can put
> this document in Documentation/media/SubmittingMediaPatches.
> 
> Alternatively, this is something we can document in our wiki.
> 
> 2) Are there DVB requirements as well for new drivers? We discussed a list of
> V4L2 requirements in Barcelona, but I wonder if there is a similar list that
> can be made for DVB drivers. Input on that will be welcome.
> 
> 3) This document describes the situation we will have when the submaintainers
> take their place early next year. So please check if I got that part right.
> 
> 4) In Barcelona we discussed 'tags' for patches to help organize them. I've
> made a proposal for those in this document. Feedback is very welcome.
> 
> 5) As discussed in Barcelona there will be git tree maintainers for specific
> platforms, but we didn't really go into detail who would be responsible for
> which platform. If you want to maintain a particular platform, then please
> let me know.
> 
> 6) The patchwork section is very short at the moment. It should be extended
> when patchwork gets support to recognize the various tags.
> 
> 7) Anything else that should be discussed here?

How to submit patches for a stable kernel.

I can never remember, and I'm sure I'm not the only one :-)

Regards,

	Hans

  parent reply	other threads:[~2012-12-11 13:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 13:07 RFC: First draft of guidelines for submitting patches to linux-media Hans Verkuil
2012-12-10 15:56 ` Frank Schäfer
2012-12-10 16:27   ` Hans Verkuil
2012-12-10 17:38     ` Mauro Carvalho Chehab
2012-12-10 17:45       ` Antti Palosaari
2012-12-10 18:43         ` Mauro Carvalho Chehab
2012-12-10 19:17       ` Frank Schäfer
2012-12-10 19:40         ` Mauro Carvalho Chehab
2012-12-11 20:41           ` Frank Schäfer
2012-12-10 18:33 ` Mauro Carvalho Chehab
2012-12-10 23:52   ` Laurent Pinchart
2012-12-11 10:29     ` Mauro Carvalho Chehab
2012-12-11 11:39       ` Laurent Pinchart
2012-12-11 12:59         ` Mauro Carvalho Chehab
2012-12-11 11:50       ` Hans Verkuil
2012-12-11 12:20         ` Laurent Pinchart
2012-12-11 15:13           ` Mauro Carvalho Chehab
2012-12-11 14:31         ` Mauro Carvalho Chehab
2012-12-11 13:15 ` Hans Verkuil [this message]
2012-12-11 15:17   ` Mauro Carvalho Chehab

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=201212111415.31483.hverkuil@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.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).