From: Sakari Ailus <sakari.ailus@iki•fi>
To: Randy Dunlap <rdunlap@infradead•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-media <linux-media@vger•kernel.org>
Subject: Re: linux-next: Tree for Apr 10 (media/i2c/adp1653)
Date: Fri, 10 Apr 2015 22:57:47 +0300 [thread overview]
Message-ID: <20150410195747.GI20756@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <55280783.20405@infradead.org>
Hi Randy and others,
On Fri, Apr 10, 2015 at 10:25:23AM -0700, Randy Dunlap wrote:
...
> > ../drivers/media/i2c/adp1653.c:433:6: warning: unused variable 'gpio' [-Wunused-variable]
> > int gpio;
A preliminary patch for adp1653 DT support was accidentally merged to
media-tree. It's now reverted in media-tree:
---
commit be8e58d93fba531b12ef2fce4fb33c9c5fb5b69f
Author: Mauro Carvalho Chehab <mchehab@osg•samsung.com>
Date: Thu Apr 9 07:33:45 2015 -0300
Revert "[media] Add device tree support to adp1653 flash driver"
As requested by Sakari:
"The driver changes are still being reviewed.
It's been proposed that the max-microamp property be renamed."
So, as the DT bindings are not agreed upstream yet, let's revert
it.
Requested-by: Sakari Ailus <sakari.ailus@iki•fi>
This reverts commit b6100f10bdc2019a65297d2597c388de2f7dd653.
---
I thus believe the problem in linux-next should disappear by itself. In the
meantime, the revert from media-tree could be used if needed.
Thanks.
--
Kind regards,
Sakari Ailus
e-mail: sakari.ailus@iki•fi XMPP: sailus@retiisi•org.uk
prev parent reply other threads:[~2015-04-10 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 11:18 linux-next: Tree for Apr 10 Stephen Rothwell
2015-04-10 17:06 ` linux-next: Tree for Apr 10 (media/i2c/ov2659) Randy Dunlap
2015-04-10 17:23 ` linux-next: Tree for Apr 10 (media/i2c/adp1653) Randy Dunlap
2015-04-10 17:25 ` Randy Dunlap
2015-04-10 19:57 ` Sakari Ailus [this message]
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=20150410195747.GI20756@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki$(echo .)fi \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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