From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Afzal Mohammed <afzal@ti.com>
Cc: linux-kernel@vger.kernel.org, lrg@ti.com, sameo@linux.intel.com,
nsekhar@ti.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: TPS65910: Improvements
Date: Fri, 4 Nov 2011 15:24:11 +0000 [thread overview]
Message-ID: <20111104152411.GB28615@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1320410912-20293-1-git-send-email-afzal@ti.com>
On Fri, Nov 04, 2011 at 06:18:32PM +0530, Afzal Mohammed wrote:
> Two changes,
...should be in two separate commits.
> 2. struct tps65910_platform_data usage can be avoided
> by making use of struct tps65910_board to simplify
> driver. Hence remove it
Why is this a simplification? Note that one of the reasons platform
data is kept separate from any runtime data the device needs is that it
makes the configuration available easier to see and understand.
next prev parent reply other threads:[~2011-11-04 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 12:48 [PATCH 1/2] mfd: TPS65910: Improvements Afzal Mohammed
2011-11-04 15:24 ` Mark Brown [this message]
2011-11-04 15:43 ` Mohammed, Afzal
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=20111104152411.GB28615@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=afzal@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=nsekhar@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