From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: [GIT PULL for v4.1] smiapp DT u64 property workaround removal
Date: Sun, 08 Mar 2015 01:15:38 +0200 [thread overview]
Message-ID: <1573085.ZVIDUf0yP4@avalon> (raw)
In-Reply-To: <20150307220634.GD6539@valkosipuli.retiisi.org.uk>
Hi Sakari,
On Sunday 08 March 2015 00:06:34 Sakari Ailus wrote:
> Hi Mauro,
>
> This pull request reverts the smiapp driver's u64 array DT property read
> workaround, and uses of_property_read_u64_array() (second patch) which is
> the correct API function for reading u64 arrays from DT.
>
> Please pull.
>
>
> The following changes since commit 3d945be05ac1e806af075e9315bc1b3409adae2b:
>
> [media] mn88473: simplify bandwidth registers setting code (2015-03-03
> 13:09:12 -0300)
>
> are available in the git repository at:
>
> ssh://linuxtv.org/git/sailus/media_tree.git smiapp-dt
>
> for you to fetch changes up to 5f36db86e0cbb48c102fee8a3fe2b98a33f13199:
>
> smiapp: Use of_property_read_u64_array() to read a 64-bit number array
> (2015-03-08 00:00:20 +0200)
>
> ----------------------------------------------------------------
> Sakari Ailus (2):
> Revert "[media] smiapp: Don't compile of_read_number() if CONFIG_OF
> isn't defined"
> smiapp: Use of_property_read_u64_array() to read a 64-bit number array
Won't this cause a bisection breakage if CONFIG_OF isn't enabled ?
> drivers/media/i2c/smiapp/smiapp-core.c | 28 +++++-----------------------
> 1 file changed, 5 insertions(+), 23 deletions(-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-03-07 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 22:06 [GIT PULL for v4.1] smiapp DT u64 property workaround removal Sakari Ailus
2015-03-07 23:15 ` Laurent Pinchart [this message]
2015-03-07 23:20 ` Sakari Ailus
2015-03-07 23:22 ` Laurent Pinchart
2015-03-07 23:29 ` [GIT PULL v2 " 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=1573085.ZVIDUf0yP4@avalon \
--to=laurent.pinchart@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox