From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: lrg-l0cyMroinI0@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V1] regulator: tps65910: use appropriate variable names.
Date: Fri, 20 Jan 2012 12:11:52 +0000 [thread overview]
Message-ID: <20120120121152.GC18297@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1327057582-6635-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Fri, Jan 20, 2012 at 04:36:22PM +0530, Laxman Dewangan wrote:
> Renaming the variables "table" to "voltage_table" and
> "table_len" to "n_voltages" of regulator information
> to have more meaningful.
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: lrg@ti.com, linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH V1] regulator: tps65910: use appropriate variable names.
Date: Fri, 20 Jan 2012 12:11:52 +0000 [thread overview]
Message-ID: <20120120121152.GC18297@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1327057582-6635-1-git-send-email-ldewangan@nvidia.com>
On Fri, Jan 20, 2012 at 04:36:22PM +0530, Laxman Dewangan wrote:
> Renaming the variables "table" to "voltage_table" and
> "table_len" to "n_voltages" of regulator information
> to have more meaningful.
Applied, thanks.
next prev parent reply other threads:[~2012-01-20 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 11:06 [PATCH V1] regulator: tps65910: use appropriate variable names Laxman Dewangan
2012-01-20 11:06 ` Laxman Dewangan
[not found] ` <1327057582-6635-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-20 12:11 ` Mark Brown [this message]
2012-01-20 12:11 ` Mark Brown
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=20120120121152.GC18297@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lrg-l0cyMroinI0@public.gmane.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.