From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org,
Hans de Goede <hdegoede@redhat.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Tejun Heo <tj@kernel.org>, Jean Delvare <khali@linux-fr.org>
Subject: Re: [PATCH 2/2] hwmon/mc13783-adc: don't access struct mc13783 directly
Date: Mon, 2 Aug 2010 14:52:34 +0200 [thread overview]
Message-ID: <20100802125234.GB13900@pengutronix.de> (raw)
In-Reply-To: <20100802100455.GC3334@sortiz-mobl>
On Mon, Aug 02, 2010 at 12:04:56PM +0200, Samuel Ortiz wrote:
> Hi Uwe,
>
> On Mon, Aug 02, 2010 at 11:14:18AM +0200, Uwe Kleine-König wrote:
> > There is a shiny new mc13783 API function that can be used instead.
> >
> > While at it refactor the code a bit to reduce code duplication a bit.
> >
> > This removes the last user of <linux/mfd/mc13783-private.h> and so this
> > include file can go away.
> That's correct, patch applied.
> As I said, we can now move mc13783-private.h to drivers/mfd/
Actually I'd fold it into mc13783-core.c.
And I didn't do it at once because I didn't expect you to take the hwmon
change via your tree. Will send a patch later.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-08-02 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 9:14 [PATCH 1/2] mfd/mc13783: new function exposing flags Uwe Kleine-König
2010-08-02 9:14 ` [PATCH 2/2] hwmon/mc13783-adc: don't access struct mc13783 directly Uwe Kleine-König
2010-08-02 10:04 ` Samuel Ortiz
2010-08-02 12:52 ` Uwe Kleine-König [this message]
2010-08-02 13:48 ` [PATCH 3/2] mfd/mc13783: get rid of now unused private header Uwe Kleine-König
2010-08-03 10:10 ` Samuel Ortiz
2010-08-02 10:01 ` [PATCH 1/2] mfd/mc13783: new function exposing flags 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=20100802125234.GB13900@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=hdegoede@redhat.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=sameo@linux.intel.com \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®