linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@dominikbrodowski.net (Dominik Brodowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 00/10] PCMCIA soc_common re-factorization
Date: Wed, 28 Oct 2009 22:25:34 +0100	[thread overview]
Message-ID: <20091028212534.GA31361@comet.dominikbrodowski.net> (raw)
In-Reply-To: <20091027231849.GE22412@n2100.arm.linux.org.uk>

Russell,

On Tue, Oct 27, 2009 at 11:18:49PM +0000, Russell King - ARM Linux wrote:
> This is a re-post of the previous patch series, but rebased forward
> earlier on this month.  Review comments would be nice to have, or
> alternatively acks.

Acked-by / Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net> .

> Lastly, is there an active PCMCIA maintainer who should take these?

Do you have a git tree to pull from, or shall I apply each patch locally?
Alternatively, you're free to push it upstream yourself; as the PCMCIA core
is only touched in one (albeit _very_ useful) line.

Best,
	Dominik

  parent reply	other threads:[~2009-10-28 21:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 23:11 [RFC PATCH 01/10] PCMCIA: soc_common: convert to a stand alone module Russell King - ARM Linux
2009-10-27 23:11 ` [RFC PATCH 02/10] PCMCIA: soc_common: provide single socket add/remove functionality Russell King - ARM Linux
2009-10-27 23:11 ` [RFC PATCH 03/10] PCMCIA: soc_common: push socket removal down to SoC specific support Russell King - ARM Linux
2009-10-27 23:12 ` [RFC PATCH 04/10] PCMCIA: soc_common: push socket probe down into " Russell King - ARM Linux
2009-10-27 23:12 ` [RFC PATCH 05/10] PCMCIA: sa1111: wrap soc_pcmcia_socket to contain sa1111 specific data Russell King - ARM Linux
2009-10-27 23:12 ` [RFC PATCH 06/10] PCMCIA: sa1111: remove duplicated initializers Russell King - ARM Linux
2009-10-27 23:12 ` [RFC PATCH 07/10] PCMCIA: soc_common: constify soc_pcmcia_socket ops member Russell King - ARM Linux
2009-10-27 23:13 ` [RFC PATCH 08/10] PCMCIA: soc_common: remove 'dev' member from soc_pcmcia_socket Russell King - ARM Linux
2009-10-27 23:13 ` [RFC PATCH 09/10] PCMCIA: ss: allow PCI IRQs > 255 Russell King - ARM Linux
2009-10-27 23:13 ` [RFC PATCH 10/10] PCMCIA: stop duplicating pci_irq in soc_pcmcia_socket Russell King - ARM Linux
2009-12-04 16:27   ` [PATCH] pcmcia: Fix additional platforms after removal of skt->irq in 66024db57d5b9011e274b314affad68f370c0d6f Jonathan Cameron
2009-12-04 16:31     ` Jonathan Cameron
2009-10-27 23:18 ` [RFC PATCH 00/10] PCMCIA soc_common re-factorization Russell King - ARM Linux
2009-10-27 23:21   ` Russell King - ARM Linux
2009-10-28  8:44   ` Wolfram Sang
2009-10-28 21:25   ` Dominik Brodowski [this message]
2009-10-29 17:25     ` Russell King - ARM Linux
2009-11-02 17:21       ` Dominik Brodowski
2009-12-04 17:18 ` [RFC PATCH 01/10] PCMCIA: soc_common: convert to a stand alone module Jonathan Cameron
2009-12-04 17:24   ` Russell King - ARM Linux
2009-12-05  9:56     ` Dominik Brodowski
2009-12-05 10:28       ` Russell King - ARM Linux
2009-12-05 11:04         ` Dominik Brodowski
2009-12-05 11:29           ` Russell King - ARM Linux

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=20091028212534.GA31361@comet.dominikbrodowski.net \
    --to=linux@dominikbrodowski.net \
    --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).