All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grazvydas Ignotas <notasas@gmail.com>
To: Kyle Manna <kyle@kylemanna.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/3] twl4030-madc: copy the device pointer
Date: Thu, 11 Aug 2011 12:50:08 +0300	[thread overview]
Message-ID: <CANOLnOMrQ7R6X+7WPjjrSZZ_3YJ2M=aaGsz_450XE2qVV2MNzA@mail.gmail.com> (raw)
In-Reply-To: <1313033272-16774-2-git-send-email-kyle@kylemanna.com>

You need to send this one to mfd maintainer, separate from this series
perhaps (see MAINTAINERS or just use ./scripts/get_maintainer.pl).

On Thu, Aug 11, 2011 at 6:27 AM, Kyle Manna <kyle@kylemanna.com> wrote:
> Worst case this fixes the following error:
> [   72.086212] (NULL device *): conversion timeout!
>
> Best case it prevents a crash
>
> Signed-off-by: Kyle Manna <kyle@kylemanna.com>
> ---
>  drivers/mfd/twl4030-madc.c |    5 ++++-
>  1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mfd/twl4030-madc.c b/drivers/mfd/twl4030-madc.c
> index b5d598c..8ef7801 100644
> --- a/drivers/mfd/twl4030-madc.c
> +++ b/drivers/mfd/twl4030-madc.c
> @@ -706,6 +706,9 @@ static int __devinit twl4030_madc_probe(struct platform_device *pdev)
>        if (!madc)
>                return -ENOMEM;
>
> +       /* Copy the pointer to device struct */
> +       madc->dev = &pdev->dev;
> +

This comment is not useful, it's already clear you are copying a pointer.

>        /*
>         * Phoenix provides 2 interrupt lines. The first one is connected to
>         * the OMAP. The other one can be connected to the other processor such
> @@ -733,7 +736,7 @@ static int __devinit twl4030_madc_probe(struct platform_device *pdev)
>        ret = twl_i2c_write_u8(TWL4030_MODULE_MAIN_CHARGE,
>                               regval, TWL4030_BCI_BCICTL1);
>        if (ret) {
> -               dev_err(&pdev->dev, "unable to write reg BCI Ctl1 0x%X\n",
> +               dev_err(&pdev->dev, "unable to write reg BCI CTL1 0x%X\n",
>                        TWL4030_BCI_BCICTL1);

Stray change (no mention in commit message), should not be part of this patch.

>                goto err_i2c;
>        }
> --
> 1.7.4.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

-- 
Gražvydas
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" 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:[~2011-08-11  9:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11  3:27 [PATCH 0/3] Fixes to twl4030-madc and add BeagleBoard support Kyle Manna
2011-08-11  3:27 ` [PATCH 1/3] twl4030-madc: copy the device pointer Kyle Manna
2011-08-11  9:50   ` Grazvydas Ignotas [this message]
2011-08-11  3:27 ` [PATCH 2/3] twl4030-madc: turn on the MADC clock Kyle Manna
2011-08-11  9:55   ` Grazvydas Ignotas
2011-08-11  3:27 ` [PATCH 3/3] BeagleBoard: add support for the twl4030-madc Kyle Manna
2011-08-11  9:44   ` Grazvydas Ignotas
2011-08-12  3:33     ` [PATCH v2 0/4] Fixes to twl4030-madc and add BeagleBoard support Kyle Manna
2011-08-12  3:33       ` [PATCH v2 1/4] mfd: twl4030-madc: copy the device pointer Kyle Manna
2011-08-12  3:33       ` [PATCH v2 2/4] mfd: twl4030-madc: turn on the MADC clock Kyle Manna
2011-08-12  3:33       ` [PATCH v2 3/4] mfd: twl4030-madc: check for NULL pointer Kyle Manna
2011-08-12  3:33       ` [PATCH v2 4/4] arm: BeagleBoard: add support for the twl4030-madc Kyle Manna
2011-09-28 18:31         ` Tony Lindgren
2011-09-28 18:31           ` Tony Lindgren
2011-08-22 13:55       ` [PATCH v2 0/4] Fixes to twl4030-madc and add BeagleBoard support Samuel Ortiz
2011-08-22 13:55         ` Samuel Ortiz
2011-08-22 13:55         ` Samuel Ortiz
2011-09-28 18:32         ` Tony Lindgren
2011-09-28 18:32           ` Tony Lindgren
2011-10-04 10:28           ` Samuel Ortiz
2011-10-04 10:28             ` Samuel Ortiz
2011-10-04 10:28             ` Samuel Ortiz

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='CANOLnOMrQ7R6X+7WPjjrSZZ_3YJ2M=aaGsz_450XE2qVV2MNzA@mail.gmail.com' \
    --to=notasas@gmail.com \
    --cc=kyle@kylemanna.com \
    --cc=linux-omap@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.