public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
	Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-media@vger.kernel.org,
	devicetree <devicetree@vger.kernel.org>,
	Jacopo Mondi <jacopo@jmondi.org>,
	"H . Nikolaus Schaller" <hns@goldelico.com>,
	"H . Nikolaus Schaller" <hns@goldelico.com>,
	Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v2 2/2] media: ov9650: add device tree binding
Date: Fri, 12 Jan 2018 15:15:44 +0100	[thread overview]
Message-ID: <438bc4cb-6486-8013-80aa-9e2253941fb8@samsung.com> (raw)
In-Reply-To: <20180108093513.nvr2e7vbt7imai2p@paasikivi.fi.intel.com>

On 01/08/2018 10:35 AM, Sakari Ailus wrote:
 
> I was going to say you're missing the MAINTAINERS entry for this newly
> added file but then I noticed that the entire driver is missing an entry.
> Still this file should have a MAINTAINERS entry added for it independently
> of that, in the same patch.
> 
> Cc Sylwester.

I don't the hardware and I can't test the patches so Mita-san if you wish
so please add yourself as a maintainer of whole driver.

-- 
Regards,
Sylwester

  reply	other threads:[~2018-01-12 14:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 16:54 [PATCH v2 0/2] media: ov9650: support device tree probing Akinobu Mita
2018-01-07 16:54 ` [PATCH v2 1/2] " Akinobu Mita
2018-01-08  9:18   ` jacopo mondi
2018-01-08  9:37     ` Sakari Ailus
2018-01-08 10:29       ` jacopo mondi
2018-01-12 14:14   ` Sylwester Nawrocki
2018-01-13 16:08     ` Akinobu Mita
2018-01-07 16:54 ` [PATCH v2 2/2] media: ov9650: add device tree binding Akinobu Mita
2018-01-08  9:35   ` Sakari Ailus
2018-01-12 14:15     ` Sylwester Nawrocki [this message]
2018-01-13 16:10       ` Akinobu Mita
2018-01-11 20:40   ` Rob Herring

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=438bc4cb-6486-8013-80aa-9e2253941fb8@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=akinobu.mita@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hns@goldelico.com \
    --cc=jacopo@jmondi.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox