From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org, Leon Luo <leonl@leopardimaging.com>
Subject: Re: [GIT PULL for 4.15] More sensor driver patches
Date: Mon, 16 Oct 2017 17:00:40 -0700 [thread overview]
Message-ID: <20171016170040.3fbb9e9a@vela.lan> (raw)
In-Reply-To: <20171013222345.x33ft5s7qspolf3k@valkosipuli.retiisi.org.uk>
Em Sat, 14 Oct 2017 01:23:45 +0300
Sakari Ailus <sakari.ailus@iki.fi> escreveu:
> Hi Mauro,
>
> Here's the second set of sensor driver patches for 4.15.
>
> Please pull.
>
>
> The following changes since commit 8382e556b1a2f30c4bf866f021b33577a64f9ebf:
>
> Simplify major/minor non-dynamic logic (2017-10-11 15:32:11 -0400)
>
> are available in the git repository at:
>
> ssh://linuxtv.org/git/sailus/media_tree.git for-4.15-2
>
> for you to fetch changes up to 5164fc93c2d8c2e9a2de1461bfba9d6b2911ce9e:
>
> imx274: V4l2 driver for Sony imx274 CMOS sensor (2017-10-14 01:06:10 +0300)
>
> ----------------------------------------------------------------
> Leon Luo (2):
> imx274: device tree binding file
> imx274: V4l2 driver for Sony imx274 CMOS sensor
As checkpatch complained:
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#69:
new file mode 100644
Who will maintain this driver?
Regards,
Mauro
Cheers,
Mauro
next prev parent reply other threads:[~2017-10-17 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 22:23 [GIT PULL for 4.15] More sensor driver patches Sakari Ailus
2017-10-17 0:00 ` Mauro Carvalho Chehab [this message]
[not found] ` <CADu3m9wEkSo=9wU2eoeA4Q5ptLL8__C5-vXYwhVCH+iTafiOSw@mail.gmail.com>
2017-10-17 7:34 ` Sakari Ailus
2017-10-25 10:24 ` Sakari Ailus
2017-10-26 6:58 ` Leon Luo
-- strict thread matches above, loose matches on Subject: below --
2017-10-19 15:16 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=20171016170040.3fbb9e9a@vela.lan \
--to=mchehab@infradead.org \
--cc=leonl@leopardimaging.com \
--cc=linux-media@vger.kernel.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 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.