From: Samuel Ortiz <sameo@linux.intel.com>
To: Haojian Zhuang <haojian.zhuang@gmail.com>
Cc: a.zummo@towertech.it, rtc-linux@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: max8925: transfer rtc irq in resources
Date: Fri, 29 Jun 2012 18:17:05 +0200 [thread overview]
Message-ID: <20120629161705.GP22806@sortiz-mobl> (raw)
In-Reply-To: <1338890930-24724-1-git-send-email-haojian.zhuang@gmail.com>
Hi Haojian,
On Tue, Jun 05, 2012 at 06:08:50PM +0800, Haojian Zhuang wrote:
> MAX8925 rtc irq is transfered from mfd resources now.
>
> Signed-off-by: Haojian Zhuang <haojian.zhuang@gmail.com>
> ---
> drivers/mfd/max8925-core.c | 8 ++++----
> drivers/rtc/rtc-max8925.c | 13 +++++++------
> 2 files changed, 11 insertions(+), 10 deletions(-)
Applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2012-06-29 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 10:08 [PATCH] mfd: max8925: transfer rtc irq in resources Haojian Zhuang
2012-06-29 16:17 ` Samuel Ortiz [this message]
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=20120629161705.GP22806@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=a.zummo@towertech.it \
--cc=haojian.zhuang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.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