From: ben@simtec.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 0/4] Simtec patches for new Kirkwood based boad
Date: Tue, 20 Apr 2010 10:26:17 +0100 [thread overview]
Message-ID: <20100420092617.075835456@fluff.org.uk> (raw)
A fix for the RTC driver, updates for using RnB with the Orion NAND
driver and the machine definition for the DTCOMMOD.
Is there anytone currently picking up mach-kirkwood patches or should
this go to Russell's patch tracker?
--
Ben (ben at fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next reply other threads:[~2010-04-20 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 9:26 Ben Dooks [this message]
2010-04-20 9:26 ` [patch 1/4] orion/kirkwood: add RnB line support to orion mtd driver Ben Dooks
2010-04-28 13:49 ` Artem Bityutskiy
2010-04-20 9:26 ` [patch 2/4] kirkwood: allow machines to register RnB callback Ben Dooks
2010-04-20 9:26 ` [patch 3/4] rtc-mv: Fix 12/24 hour error message Ben Dooks
2010-04-20 9:26 ` [patch 4/4] ARM: kirkwood: Add Datong DTCOMMOD machine definition Ben Dooks
2010-04-20 16:58 ` Nicolas Pitre
2010-04-20 17:02 ` [patch 0/4] Simtec patches for new Kirkwood based boad Nicolas Pitre
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=20100420092617.075835456@fluff.org.uk \
--to=ben@simtec.co.uk \
--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).