All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org
Subject: [GIT PULL for 4.19] ov2680 driver and dw9807 driver rename
Date: Wed, 25 Jul 2018 15:48:17 +0300	[thread overview]
Message-ID: <20180725124816.z26t5cvwsjkvlytd@valkosipuli.retiisi.org.uk> (raw)

Hi Mauro,

Here's a driver for the ov2680 sensor and a patch that renamed dw0807 as
dw9807-vcm for it's a driver for the VCM bit only. Rename it now to avoid
Kconfig option fuss for most people.

Please pull.


The following changes since commit 8601494e0ec0a7697230b2abca25d786b793341b:

  media: media-ioc-enum-entities.rst/-g-topology.rst: clarify ID/name usage (2018-07-25 08:05:06 -0400)

are available in the git repository at:

  ssh://linuxtv.org/git/sailus/media_tree.git for-4.19-4

for you to fetch changes up to 070438e314c5f7f8bbb6d7af9bfc4cf20f33a275:

  dw9807-vcm: Recognise this is just the VCM bit of the device (2018-07-25 15:45:08 +0300)

----------------------------------------------------------------
Rui Miguel Silva (2):
      media: ov2680: dt: Add bindings for OV2680
      media: ov2680: Add Omnivision OV2680 sensor driver

Sakari Ailus (1):
      dw9807-vcm: Recognise this is just the VCM bit of the device

 .../devicetree/bindings/media/i2c/ov2680.txt       |   46 +
 drivers/media/i2c/Kconfig                          |   14 +-
 drivers/media/i2c/Makefile                         |    3 +-
 drivers/media/i2c/{dw9807.c => dw9807-vcm.c}       |    0
 drivers/media/i2c/ov2680.c                         | 1186 ++++++++++++++++++++
 5 files changed, 1247 insertions(+), 2 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/media/i2c/ov2680.txt
 rename drivers/media/i2c/{dw9807.c => dw9807-vcm.c} (100%)
 create mode 100644 drivers/media/i2c/ov2680.c

-- 
Sakari Ailus
e-mail: sakari.ailus@iki.fi

                 reply	other threads:[~2018-07-25 13:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180725124816.z26t5cvwsjkvlytd@valkosipuli.retiisi.org.uk \
    --to=sakari.ailus@iki.fi \
    --cc=linux-media@vger.kernel.org \
    /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.