linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	media-workshop@linuxtv.org,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: drivers without explicit MAINTAINERS entry - was: Re: [media-workshop] Tentative Agenda for the November workshop
Date: Mon, 12 Nov 2012 08:37:15 -0200	[thread overview]
Message-ID: <20121112083715.3d9a6b37@redhat.com> (raw)
In-Reply-To: <20121110205522.GJ25623@valkosipuli.retiisi.org.uk>

Hi Sakari,

Em Sat, 10 Nov 2012 22:55:22 +0200
Sakari Ailus <sakari.ailus@iki.fi> escreveu:

> Hi Mauro,
> 
> On Fri, Nov 02, 2012 at 11:13:10AM -0200, Mauro Carvalho Chehab wrote:
> ...
> These are "Maintained" by me (with Laurent):
> 
> > i2c/adp1653.ko                 = i2c/adp1653.c
> > i2c/as3645a.ko                 = i2c/as3645a.c
> 
> "Maintained" by me:
> 
> > i2c/smiapp-pll.ko              = i2c/smiapp-pll.c
> > i2c/smiapp/smiapp.ko           = i2c/smiapp/smiapp-core.c i2c/smiapp/smiapp-regs.c i2c/smiapp/smiapp-quirk.c i2c/smiapp/smiapp-limits.c
> 
> "Odd fixes":
> 
> > i2c/tcm825x.ko                 = i2c/tcm825x.c
> > platform/omap2cam.ko           = platform/omap24xxcam.c platform/omap24xxcam-dma.c
> 
> Regards,
> 


Care to send us a patch with the above? It is likely better to have one entry per
driver, to reduce the risk of merge conflicts upstream.

-- 
Regards,
Mauro

  reply	other threads:[~2012-11-12 10:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22  8:35 Tentative Agenda for the November workshop Hans Verkuil
2012-10-22 10:39 ` [media-workshop] " Laurent Pinchart
2012-10-22 10:53   ` Sylwester Nawrocki
2012-10-22 10:57     ` Alain VOLMAT
2012-10-22 11:17       ` Sylwester Nawrocki
2012-10-22 11:18     ` Laurent Pinchart
2012-10-22 12:06       ` Hans Verkuil
2012-10-23  1:03         ` Laurent Pinchart
2012-10-23  6:46           ` Hans Verkuil
2012-10-23 10:22             ` Laurent Pinchart
2012-10-23 11:59               ` Sylwester Nawrocki
2012-10-24 22:42                 ` Laurent Pinchart
2012-10-25  8:43                   ` Sylwester Nawrocki
2012-10-25  8:52                     ` Hans Verkuil
2012-10-22 21:13       ` Guennadi Liakhovetski
2012-10-22 21:14 ` Guennadi Liakhovetski
2012-10-31 13:12   ` Guennadi Liakhovetski
2012-11-01 16:01     ` Hans Verkuil
2012-11-01 16:05       ` Laurent Pinchart
2012-11-01 19:01         ` Sylwester Nawrocki
2012-10-25 17:27 ` Mauro Carvalho Chehab
2012-11-01 15:44   ` Hans Verkuil
2012-11-01 16:12     ` Mauro Carvalho Chehab
2012-11-02 13:13       ` drivers without explicit MAINTAINERS entry - was: " Mauro Carvalho Chehab
2012-11-02 13:47         ` Hans Verkuil
2012-11-02 14:34           ` Mauro Carvalho Chehab
2012-11-02 15:05             ` [media-workshop] drivers without explicit MAINTAINERS entry - was: " Palash Bandyopadhyay
2012-11-12 18:41             ` drivers without explicit MAINTAINERS entry - was: Re: [media-workshop] " Alexey Klimov
2012-11-12 18:54               ` Mauro Carvalho Chehab
2012-11-23 10:31               ` Hans Verkuil
2012-11-25 23:18                 ` Alexey Klimov
2012-11-26 14:15                   ` Hans Verkuil
2012-11-26 14:21                     ` Alexey Klimov
2012-11-03  9:25         ` [PATCH] firedtv: add MAINTAINERS entry Stefan Richter
2012-11-08 14:18         ` drivers without explicit MAINTAINERS entry - was: Re: [media-workshop] Tentative Agenda for the November workshop Laurent Pinchart
2012-11-13  9:53           ` Laurent Pinchart
2012-12-10 22:01             ` martin
2012-12-11  0:11               ` Laurent Pinchart
2012-11-10 20:55         ` Sakari Ailus
2012-11-12 10:37           ` Mauro Carvalho Chehab [this message]
2012-11-12 22:14             ` [PATCH 1/1] MAINTAINERS: Update maintainer for smiapp and adp1653 drivers 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=20121112083715.3d9a6b37@redhat.com \
    --to=mchehab@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=media-workshop@linuxtv.org \
    --cc=sakari.ailus@iki.fi \
    /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).