public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: "Kim, Milo" <Milo.Kim@ti.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mfd: tps65910: remove unused data
Date: Fri, 30 Nov 2012 00:49:06 +0530	[thread overview]
Message-ID: <50B7B52A.30005@nvidia.com> (raw)
In-Reply-To: <A874F61F95741C4A9BA573A70FE3998F6418F1BB@DQHE02.ent.ti.com>

On Thursday 29 November 2012 02:18 PM, Kim, Milo wrote:
>   The 'io_mutex' is not used anywhere.
>   The regmap API supports the mutex internally, so no additional mutex required.
>
>   And 'domain' private data is unnecessary because the irq domain is
>   already registered by using regmap_add_irq_chip().
>
> Signed-off-by: Milo(Woogyom) Kim<milo.kim@ti.com>
> ---

Thanks, I missed on my cleanups.

Acked-by: Laxman Dewangan <ldewangan@nvidia.com>
>   drivers/mfd/tps65910.c       |    1 -
>   include/linux/mfd/tps65910.h |    2 --
>   2 files changed, 3 deletions(-)
>
> diff --git a/drivers/mfd/tps65910.c b/drivers/mfd/tps65910.c
> index fdb3027..d5ef3a5 100644
> --- a/drivers/mfd/tps65910.c
> +++ b/drivers/mfd/tps65910.c
> @@ -486,7 +486,6 @@ static __devinit int tps65910_i2c_probe(struct i2c_client *i2c,
>   	tps65910->dev =&i2c->dev;
>   	tps65910->i2c_client = i2c;
>   	tps65910->id = chip_id;
> -	mutex_init(&tps65910->io_mutex);
>
>   	tps65910->regmap = devm_regmap_init_i2c(i2c,&tps65910_regmap_config);
>   	if (IS_ERR(tps65910->regmap)) {
> diff --git a/include/linux/mfd/tps65910.h b/include/linux/mfd/tps65910.h
> index 0b16903..20e433e 100644
> --- a/include/linux/mfd/tps65910.h
> +++ b/include/linux/mfd/tps65910.h
> @@ -893,7 +893,6 @@ struct tps65910 {
>   	struct device *dev;
>   	struct i2c_client *i2c_client;
>   	struct regmap *regmap;
> -	struct mutex io_mutex;
>   	unsigned int id;
>
>   	/* Client devices */
> @@ -907,7 +906,6 @@ struct tps65910 {
>   	/* IRQ Handling */
>   	int chip_irq;
>   	struct regmap_irq_chip_data *irq_data;
> -	struct irq_domain *domain;
>   };
>
>   struct tps65910_platform_data {


  reply	other threads:[~2012-11-29 19:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29  8:48 [PATCH 1/2] mfd: tps65910: remove unused data Kim, Milo
2012-11-29 19:19 ` Laxman Dewangan [this message]
2012-11-30 11:22 ` 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=50B7B52A.30005@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=Milo.Kim@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --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