From: viresh.kumar@st.com (viresh kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [rtc-linux] Re: [PATCH V4 resend] rtc: Adding support for spear rtc
Date: Mon, 25 Apr 2011 16:51:15 +0530 [thread overview]
Message-ID: <4DB5592B.4060707@st.com> (raw)
In-Reply-To: <20110425111150.GE4768@sirena.org.uk>
On 04/25/2011 04:41 PM, Mark Brown wrote:
> On Mon, Apr 25, 2011 at 04:29:25PM +0530, viresh kumar wrote:
>
>> > We have been waiting for response from rtc's mailing list from a very long time,
>> > but didn't got any feedback till date.
>> > As this driver is specific to SPEAr, can we get this added through arm's tree??
> Generally Andrew Morton ends up taking RTC patches - you should probably
> resend with a copy to him.
Thanks Mark,
I also got this impression after looking in git log for rtc-patches, but
wasn't sure. But now i am.
--
viresh
prev parent reply other threads:[~2011-04-25 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 10:36 [PATCH V4 resend] rtc: Adding support for spear rtc Viresh Kumar
2011-02-17 9:03 ` viresh kumar
2011-04-25 10:59 ` viresh kumar
2011-04-25 11:11 ` [rtc-linux] " Mark Brown
2011-04-25 11:21 ` viresh kumar [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=4DB5592B.4060707@st.com \
--to=viresh.kumar@st.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).