Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-iio@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	Naveen Krishna Chatradhi <ch.naveen@samsung.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Doug Anderson <dianders@chromium.org>,
	Tomasz Figa <tomasz.figa@gmail.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH 1/4] iio: max1363: Use devm_ functions whereever possible to allocate resources
Date: Sun, 03 Feb 2013 18:02:57 +0000	[thread overview]
Message-ID: <510EA651.6040509@kernel.org> (raw)
In-Reply-To: <20130203171852.GA29574@roeck-us.net>

On 02/03/2013 05:18 PM, Guenter Roeck wrote:
> On Sun, Feb 03, 2013 at 12:10:32PM +0000, Jonathan Cameron wrote:
>> On 02/03/2013 12:59 AM, Guenter Roeck wrote:
>>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>> Applied to togreg branch of iio.git.
>>
>> Note I'll probably rebase the togreg branch if / when Greg has pulled
>> last pull request (sent a few mins ago) so as to get a directly
>> applied fix for this driver.
>>
> No problem.
> 
> There is some dead code in the max1363 driver.
> 
> drivers/iio/adc/max1363.c:1492:12: warning: 'max1363_register_buffered_funcs_and_init' defined but not used [-Wunused-function]
> drivers/iio/adc/max1363.c:1527:13: warning: 'max1363_buffer_cleanup' defined but not used [-Wunused-function]
> 
> I thought I had seen a note on the iio mailing list that you wanted to submit a patch for it,

Went out yesterday as [PATCH] iio:max1363 remove some functions left after merge

> but I didn't see it yet. Or maybe my memory is wrong, or you were talking about
> something else.

It's gone to Greg who added it staging-next yesterday (rather than throw the iio tree).
I actually intended to get his Ack on it (as the merge that caused it was I think
his), but he applied it directly. Anyhow, that's the reason staging-next with that patch
will differ from iio.git and hence why I'll rebase once the current pull request is
dealt with.

> 
> Want me to submit a patch (assuming the fix is simply to remove the above functions) ?

All sorted if via an indirect route.

> 
> Thanks,
> Guenter
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2013-02-03 18:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-03  0:59 [RFC v2 0/4] iio: Devicetree support Guenter Roeck
2013-02-03  0:59 ` [PATCH 1/4] iio: max1363: Use devm_ functions whereever possible to allocate resources Guenter Roeck
2013-02-03 12:10   ` Jonathan Cameron
2013-02-03 17:18     ` Guenter Roeck
2013-02-03 18:02       ` Jonathan Cameron [this message]
2013-02-03 18:16         ` Guenter Roeck
2013-02-03  0:59 ` [PATCH v2 2/4] iio/adc: (max1363) Add support for external reference voltage Guenter Roeck
2013-02-03 12:12   ` Jonathan Cameron
2013-02-03  0:59 ` [PATCH RFC 3/4] iio: Update iio_channel_get API to use consumer device pointer as argument Guenter Roeck
2013-02-03  0:59 ` [PATCH v2 4/4] iio: Add OF support Guenter Roeck
2013-02-03  1:30   ` Tomasz Figa
2013-02-03  2:06     ` Guenter Roeck
2013-02-03 11:29       ` Lars-Peter Clausen
2013-02-03 11:52         ` Tomasz Figa
2013-02-03 12:22           ` Lars-Peter Clausen
2013-02-03 17:01           ` Guenter Roeck
2013-02-03 17:30             ` Tomasz Figa
2013-02-03 18:55               ` Lars-Peter Clausen
2013-02-03 20:58                 ` Jonathan Cameron
2013-02-03 22:44                   ` Lars-Peter Clausen
2013-02-03 23:14                 ` Tomasz Figa
2013-02-04 17:12                   ` Guenter Roeck
2013-02-04 17:41                     ` Lars-Peter Clausen
2013-02-04 17:51                     ` Guenter Roeck
2013-02-04 18:00                       ` Tomasz Figa
2013-02-04 18:09                         ` Guenter Roeck
2013-02-03 16:31         ` Guenter Roeck
2013-02-03 19:00           ` Lars-Peter Clausen
2013-02-03 14:17   ` Lars-Peter Clausen
2013-02-03 16:22     ` Guenter Roeck
2013-02-04 16:37       ` Guenter Roeck

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=510EA651.6040509@kernel.org \
    --to=jic23@kernel.org \
    --cc=ch.naveen@samsung.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dianders@chromium.org \
    --cc=grant.likely@secretlab.ca \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=rob.herring@calxeda.com \
    --cc=tomasz.figa@gmail.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