From: Jonathan Cameron <jic23@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-iio@vger.kernel.org, linux-input@vger.kernel.org,
Jonathan Cameron <jic23@cam.ac.uk>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>, Felipe Balbi <balbi@ti.com>,
Patil Rachna <rachna@ti.com>
Subject: Re: [PATCH 4/7] iio/ti_am335x_adc: remove the else case
Date: Wed, 22 May 2013 22:55:41 +0100 [thread overview]
Message-ID: <519D3EDD.2000104@kernel.org> (raw)
In-Reply-To: <1369256897-25984-4-git-send-email-bigeasy@linutronix.de>
On 05/22/2013 10:08 PM, Sebastian Andrzej Siewior wrote:
> The DT support added in ("iio: adc: am335x: Add DT support")
> added an else case which shifts the code to the righ for no reaseon.
> This patch simply removes the pointless else case and shifts the code
> back to the left.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Either I am going completely mad or I never took the original patch.
I'm not entirely sure I can remember why though. I think there were
issues with another patch in the series and so I was waiting for
a reposting that never happened. Looking back I think the debate
was curriously enough whether it made sense ot have the platform_data
support in there or not.
Did anyone every take any of that series? Which tree did you base these on?
> ---
> drivers/iio/adc/ti_am335x_adc.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/iio/adc/ti_am335x_adc.c b/drivers/iio/adc/ti_am335x_adc.c
> index f258eb0..ac78672 100644
> --- a/drivers/iio/adc/ti_am335x_adc.c
> +++ b/drivers/iio/adc/ti_am335x_adc.c
> @@ -214,14 +214,11 @@ static int tiadc_probe(struct platform_device *pdev)
> node = of_get_child_by_name(node, "adc");
> if (!node)
> return -EINVAL;
> - else {
> - err = of_property_read_u32(node,
> - "ti,adc-channels", &val32);
> - if (err < 0)
> - goto err_free_device;
> - else
> - adc_dev->channels = val32;
> - }
> + err = of_property_read_u32(node,
> + "ti,adc-channels", &val32);
> + if (err < 0)
> + goto err_free_device;
> + adc_dev->channels = val32;
> }
>
> indio_dev->dev.parent = &pdev->dev;
>
next prev parent reply other threads:[~2013-05-22 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 21:08 [PATCH 1/7] input/ti_am_335x_tsc: remove the else case Sebastian Andrzej Siewior
[not found] ` <1369256897-25984-1-git-send-email-bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2013-05-22 21:08 ` [PATCH 2/7] input/ti_am33x_tsc: remove platform_data support Sebastian Andrzej Siewior
2013-05-22 21:08 ` [PATCH 3/7] input/i_am335x_tsc: removed unused variable in titsc_irq() Sebastian Andrzej Siewior
2013-05-22 21:44 ` Jonathan Cameron
2013-05-22 21:08 ` [PATCH 4/7] iio/ti_am335x_adc: remove the else case Sebastian Andrzej Siewior
2013-05-22 21:55 ` Jonathan Cameron [this message]
2013-05-31 7:43 ` Sebastian Andrzej Siewior
2013-05-22 21:08 ` [PATCH 6/7] mfd/ti_am335x_tscadc: remove platform_data support Sebastian Andrzej Siewior
2013-05-22 21:08 ` [PATCH 5/7] iio/ti_am335x_adc: " Sebastian Andrzej Siewior
2013-05-22 21:08 ` [PATCH 7/7] Documentation/DT bindings: add info for TI TSC ADC Sebastian Andrzej Siewior
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=519D3EDD.2000104@kernel.org \
--to=jic23@kernel.org \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=dmitry.torokhov@gmail.com \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=rachna@ti.com \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).