From: alexandre.belloni@free-electrons•com (Alexandre Belloni)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] ARM: at91: rm9200 add system timer resources to watchdog
Date: Fri, 31 Oct 2014 21:57:56 +0100 [thread overview]
Message-ID: <20141031205756.GB11327@piout.net> (raw)
In-Reply-To: <3170633.12AsIiHlY5@wuerfel>
On 31/10/2014 at 21:50:05 +0100, Arnd Bergmann wrote :
> On Friday 31 October 2014 21:45:58 Alexandre Belloni wrote:
> > To be able to make the watchdog driver independent from the mach/ includes, pass
> > the system timer register space as a resource.
> >
> > Also, change the name to avoid conflicting with the at91sam9 watchdog driver.
> >
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons•com>
> >
>
> Doing this change as a separate patch breaks bisection because now the device
> name no longer matches untile the other patch is applied too.
>
Yeah, I was not sure how important that was as there is no user of the
watchdog in the kernel. My thinking was that both patch can then go
through different trees.
I can definitely squash them.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-31 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 20:45 [PATCH 1/2] ARM: at91: rm9200 add system timer resources to watchdog Alexandre Belloni
2014-10-31 20:45 ` [PATCH 2/2] watchdog: at91rm9200 remove mach/ header dependency Alexandre Belloni
2014-10-31 20:53 ` Arnd Bergmann
2014-10-31 20:59 ` Alexandre Belloni
2014-10-31 20:50 ` [PATCH 1/2] ARM: at91: rm9200 add system timer resources to watchdog Arnd Bergmann
2014-10-31 20:57 ` Alexandre Belloni [this message]
2014-10-31 21:36 ` Arnd Bergmann
2014-11-04 22:41 ` Alexandre Belloni
2014-11-05 9:58 ` Arnd Bergmann
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=20141031205756.GB11327@piout.net \
--to=alexandre.belloni@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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