All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
	linux-media@vger.kernel.org, hverkuil@xs4all.nl
Subject: Re: [PATCH 1/1] MAINTAINERS: Add maintainers for Media Controller
Date: Mon, 24 Jun 2019 09:30:12 -0300	[thread overview]
Message-ID: <20190624093012.3a1b5101@coco.lan> (raw)
In-Reply-To: <20190620141955.GF5720@pendragon.ideasonboard.com>

Em Thu, 20 Jun 2019 17:19:55 +0300
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:

> Hi Sakari,
> 
> Thank you for the patch.
> 
> On Thu, Jun 20, 2019 at 05:17:53PM +0300, Sakari Ailus wrote:
> > When Media Controller was merged to mainline long, long time ago, no-one
> > bothered to think what its MAINTAINERS entry should be. Now that Media
> > Controller is moved into its own directory, address this at the same time.
> > 
> > So tell people to mail patches to myself and Laurent Pinchart.
> > 
> > Note that the patches are still merged through the Media tree, just like
> > any other driver or framework bits that have separate "mail patches to"
> > entries different from the main drivers/media one.
> > 
> > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>  
> 
> This will help me catching changes to the media controller, and being
> more active on reviews, so I welcome that change.

Ok, but please notice that this is a core part of the subsystem, and
not a driver one.

So, you should be sure that you'll have enough bandwidth to not
get patches accumulated here for no more than a reasonable time
(a couple of weeks).

If both you and Sakari are ok with that, I'll pick it.

Regards,
Mauro

  reply	other threads:[~2019-06-24 12:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20 14:17 [PATCH 1/1] MAINTAINERS: Add maintainers for Media Controller Sakari Ailus
2019-06-20 14:19 ` Laurent Pinchart
2019-06-24 12:30   ` Mauro Carvalho Chehab [this message]
2019-06-24 12:35     ` Sakari Ailus
2019-06-24 12:40     ` Laurent Pinchart
2019-06-20 14:21 ` 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=20190624093012.3a1b5101@coco.lan \
    --to=mchehab@kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.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.