From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Dove: add RTC device node
Date: Fri, 8 Mar 2013 23:12:02 +0000 [thread overview]
Message-ID: <201303082312.02189.arnd@arndb.de> (raw)
In-Reply-To: <20130308215818.GU23237@titan.lakedaemon.net>
On Friday 08 March 2013, Jason Cooper wrote:
> Applied to mvebu/fixes with the following commit entry:
>
> ARM: Dove: add RTC device node
>
> The commit:
>
> 48be9ac ARM: Dove: split legacy and DT setup
>
> removed the RTC initialization. This patch re-enables the RTC
> via the DT.
Looks good. FWIW, the style I tend to use is
|ARM: Dove: add RTC device node
|
|The commit 48be9ac "ARM: Dove: split legacy and DT setup" removed the RTC
|initialization. This patch re-enables the RTC via the DT.
I don't think that there is a wide agreement on how to refer to other
patches yet, but I do a lot of regression fixes like that, so maybe I
can start a trend here.
ARnd
next prev parent reply other threads:[~2013-03-08 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 11:13 [PATCH] ARM: Dove: add RTC device node Jean-Francois Moine
2013-03-08 20:53 ` Sergei Shtylyov
2013-03-08 21:58 ` Jason Cooper
2013-03-08 23:12 ` Arnd Bergmann [this message]
2013-03-09 3:12 ` Jason Cooper
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=201303082312.02189.arnd@arndb.de \
--to=arnd@arndb.de \
--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