From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [PATCH 13/18] MIPS: Alchemy: add RTC device to all devboards
Date: Wed, 9 Nov 2011 14:53:39 +0000 [thread overview]
Message-ID: <20111109145339.GM19187@linux-mips.org> (raw)
In-Reply-To: <1320174224-27305-14-git-send-email-manuel.lauss@googlemail.com>
Queued for 3.3. Thanks,
Ralf
next prev parent reply other threads:[~2011-11-09 14:54 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 19:03 [PATCH 00/18] MIPS: Alchemy board and driver updates Manuel Lauss
2011-11-01 19:03 ` [PATCH 01/18] MIPS: Alchemy: remove PB1000 support Manuel Lauss
2011-11-02 11:37 ` Ralf Baechle
2011-11-02 11:53 ` [PATCH RESEND " Manuel Lauss
2011-11-09 14:48 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 02/18] MIPS: Alchemy: drop MIRAGE/BOSPORUS board support Manuel Lauss
2011-11-09 14:49 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 03/18] MIPS: Alchemy: devboards: remove unneeded BCSR IRQ reg acc Manuel Lauss
2011-11-09 14:49 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 04/18] MIPS: Alchemy: Au1300 SoC support Manuel Lauss
2011-11-09 14:50 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 05/18] MIPS: Alchemy: DB1300 support Manuel Lauss
2011-11-09 14:50 ` Ralf Baechle
2011-11-09 18:38 ` [PATCH] MIPS: Alchemy: db1300: fix build: missing module.h Manuel Lauss
2011-11-09 18:48 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 06/18] MIPS: Alchemy: better DB1550 support Manuel Lauss
2011-11-09 14:50 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 07/18] MIPS: Alchemy: merge GPR/MTX-1/XXS1500 board code into single files Manuel Lauss
2011-11-09 14:50 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 08/18] MIPS: Alchemy: merge devboard code into single per-board files Manuel Lauss
2011-11-04 8:35 ` [PATCH v2 " Manuel Lauss
2011-11-09 14:50 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 09/18] MIPS: Alchemy: move au1200fb global functions to platform data Manuel Lauss
2011-11-09 14:52 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 10/18] MIPS: Alchemy: Merge PB1200 support into DB1200 code Manuel Lauss
2011-11-09 14:52 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 11/18] MIPS: Alchemy: one kernel for DB1000/DB1500/DB1100 Manuel Lauss
2011-11-09 14:53 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 12/18] MIPS: Alchemy: MMC for DB1100 Manuel Lauss
2011-11-09 14:53 ` Ralf Baechle
2011-11-09 18:39 ` [PATCH] MIPS: Alchemy: db1100: fix build: missing module.h Manuel Lauss
2011-11-09 18:55 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 13/18] MIPS: Alchemy: add RTC device to all devboards Manuel Lauss
2011-11-09 14:53 ` Ralf Baechle [this message]
2011-11-01 19:03 ` [PATCH 14/18] MTD: nand: make au1550nd.c a platform_driver Manuel Lauss
2011-11-09 14:54 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 15/18] MIPS: Alchemy: remove unused board headers Manuel Lauss
2011-11-09 14:55 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 16/18] net/irda: convert au1k_ir to platform driver Manuel Lauss
2011-11-09 14:55 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 17/18] MIPS: Alchemy: hook up IrDA on DB1000/DB1100 Manuel Lauss
2011-11-09 14:56 ` Ralf Baechle
2011-11-01 19:03 ` [PATCH 18/18] MIPS: Alchemy: Touchscreen support on DB1100 Manuel Lauss
2011-11-09 14:56 ` Ralf Baechle
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=20111109145339.GM19187@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@googlemail.com \
/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