From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] Samsung watchdog support clean-up
Date: Thu, 13 Jun 2013 21:11:03 +0200 [thread overview]
Message-ID: <2600203.AqDGG2pvxF@flatron> (raw)
In-Reply-To: <0ee601ce65c1$673f2c90$35bd85b0$%kim@samsung.com>
Hi Kukjin,
On Monday 10 of June 2013 19:00:57 Kukjin Kim wrote:
> Tomasz Figa wrote:
> > Hi Kukjin,
> >
> > On Tuesday 04 of June 2013 18:37:54 Kukjin Kim wrote:
> > > Tomasz Figa wrote:
> > > > Hi Sylwester, Kukjin,
> > >
> > > Hi,
> > >
> > > > On Saturday 01 of June 2013 10:16:52 Sylwester Nawrocki wrote:
> > > > > Hi Tomasz,
> > > > >
> > > > > On 05/19/2013 12:37 AM, Tomasz Figa wrote:
> > > > > > This series is aiming at cleaning up a bit watchdog support on
> > > > > > Samsung
> > > > > > SoCs. The patches tweak a bit all the watchdog handling code
> > > > > > here and
> > > > > > there, with the goal of making it DT- and
> > > > > > multiplatform-friendly.
> > > > > >
> > > > > > See particular patches for more detailed descriptions.
> > > > > >
> > > > > > On S3C6410-based Tiny6410 board (Mini6410-compatible):
> > > > > >
> > > > > > Tested-by: Tomasz Figa<tomasz.figa@gmail.com>
> > > > >
> > > > > I've tested this series on a s3c2440 based board. The system
> > > > > restart
> > > > > works fine.
> > > > >
> > > > > Tested-by: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
> > > >
> > > > Thank you Sylwester for testing this series.
> > >
> > > Thanks again :-)
> > >
> > > > Kukjin, since it has been already tested on s3c24xx and s3c64xx
> > > > and nobody seems to care about s5p64x0 and s5pc100 (although I
> > > > don't see a reason why these patches should break them), could we
> > > > have this series applied?> >
> > > OK, let me test this series on the smdk64x0 then, will apply.
> > >
> > > If any problems, let you know.
> > >
> > > Thanks for your gentle reminder.
> >
> > Thank you for handling this. I have a lot of patches for S3C64xx
> > depending on this series queued in my private tree and it would be
> > really nice if I could finally get them merged for 3.11.
>
> Applied, thanks.
Seems like this series got lost in action, as I don't see it in your tree.
Is there any problem with it?
Best regards,
Tomasz
next prev parent reply other threads:[~2013-06-13 19:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 22:37 [PATCH 0/6] Samsung watchdog support clean-up Tomasz Figa
2013-05-18 22:37 ` [PATCH 1/6] watchdog: s3c2410_wdt: Use local register definitions Tomasz Figa
2013-05-18 22:37 ` [PATCH 2/6] ARM: SAMSUNG: uncompress: Use local definitions of watchdog registers Tomasz Figa
2013-05-18 22:50 ` [PATCH v2 " Tomasz Figa
2013-05-18 22:37 ` [PATCH 3/6] ARM: SAMSUNG: Add watchdog reset driver Tomasz Figa
2013-05-18 22:37 ` [PATCH 4/6] ARM: SAMSUNG: Let platforms use the new " Tomasz Figa
2013-05-18 22:37 ` [PATCH 5/6] ARM: SAMSUNG: Remove legacy watchdog reset code Tomasz Figa
2013-05-18 22:37 ` [PATCH 6/6] ARM: SAMSUNG: Remove unused plat/regs-watchdog.h header Tomasz Figa
2013-06-01 8:16 ` [PATCH 0/6] Samsung watchdog support clean-up Sylwester Nawrocki
2013-06-03 12:49 ` Tomasz Figa
2013-06-04 9:37 ` Kukjin Kim
2013-06-04 9:45 ` Tomasz Figa
2013-06-10 10:00 ` Kukjin Kim
2013-06-13 19:11 ` Tomasz Figa [this message]
2013-06-13 23:22 ` Kukjin Kim
2013-06-13 23:25 ` Tomasz Figa
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=2600203.AqDGG2pvxF@flatron \
--to=tomasz.figa@gmail.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).