From: akpm@linux-foundation.org (Andrew Morton)
To: linux-arm-kernel@lists.infradead.org
Subject: [rtc-linux] RE: [PATCH 5/5] rtc: rtc-s3c: Fix debug message format on RTC
Date: Fri, 10 Sep 2010 16:23:54 -0700 [thread overview]
Message-ID: <20100910162354.9b96f1df.akpm@linux-foundation.org> (raw)
In-Reply-To: <000f01cb50dc$ba4a74a0$2edf5de0$%kim@samsung.com>
On Fri, 10 Sep 2010 20:38:39 +0900
Kukjin Kim <kgene.kim@samsung.com> wrote:
> Wan ZongShun wrote:
> >
> > 2010/9/9 Kukjin Kim <kgene.kim@samsung.com>:
> > > Ben Dooks wrote:
> > >>
> > >> On 07/09/10 06:29, Kukjin Kim wrote:
> > >> > This patch fixes debug message format on rtc-s3c.
> > >> >
> > >> > Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> > >> > Cc: Ben Dooks <ben-linux@fluff.org>
> > >> > ---
> > >> > drivers/rtc/rtc-s3c.c | 18 +++++++++---------
> > >> > 1 files changed, 9 insertions(+), 9 deletions(-)
> > >> >
> > >>
> > >> how long has this lot been broken for?
> > >>
> > > Haha...we don't know :-)
> > >
> > >> Acked-by: Ben Dooks <ben-linux@fluff.org>
> > >
> > > Thanks for your ack...so...
> > >
> > > Hi Alessandro Zummo,
> > > Is it possible to send this to upstream through your tree?
> > > Or which tree is better to care this.
> >
> >
> > Please get help from Andrew.
> >
> Ok ;-)
>
> Hello Andrew,
>
> Could you please handle following items which have been got Ben's ack?
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-September/025387.html
> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-September/025388.html
> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-September/025391.html
>
> And it's available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git next-rtc-s3c
>
> If any problems, please let me know.
>
I'd prefer to handle the whole series rather than cherrypick a subset
of it.
Patch 1/5 has a question from Ben which hasn't been responded to yet.
Patch 4/5 is due to be updated.
So please let's fix those things up, resend the entire series and cc me
on the emails?
next prev parent reply other threads:[~2010-09-10 23:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 5:29 [PATCH 0/5] rtc: rtc-s3c: Fix RTC bugs for RTC-S3C Kukjin Kim
2010-09-07 5:29 ` [PATCH 1/5] rtc: rtc-s3c: Fix access unit from byte to word on RTCCON Kukjin Kim
2010-09-07 23:17 ` Ben Dooks
2010-09-07 5:29 ` [PATCH 2/5] rtc: rtc-s3c: Fix setting missing field of getalarm Kukjin Kim
2010-09-07 23:21 ` Ben Dooks
2010-09-07 5:29 ` [PATCH 3/5] rtc: rtc-s3c: Fix on support RTC Alarm Kukjin Kim
2010-09-07 23:22 ` Ben Dooks
2010-09-07 5:29 ` [PATCH 4/5] rtc: rtc-s3c: Fix on RTC initialization method Kukjin Kim
2010-09-07 8:56 ` Kyungmin Park
2010-09-07 23:24 ` Ben Dooks
2010-09-08 1:55 ` Wan ZongShun
2010-09-09 1:03 ` Kukjin Kim
2010-09-09 1:04 ` Kukjin Kim
2010-09-07 5:29 ` [PATCH 5/5] rtc: rtc-s3c: Fix debug message format on RTC Kukjin Kim
2010-09-07 23:29 ` Ben Dooks
2010-09-09 1:11 ` Kukjin Kim
2010-09-10 9:05 ` [rtc-linux] " Wan ZongShun
2010-09-10 11:38 ` Kukjin Kim
2010-09-10 23:23 ` Andrew Morton [this message]
2010-09-10 23:35 ` Kukjin Kim
2010-10-07 23:16 ` Kukjin Kim
2010-10-07 23:28 ` Andrew Morton
2010-10-07 23:46 ` Kukjin Kim
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=20100910162354.9b96f1df.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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).