From: linux@dominikbrodowski.net (Dominik Brodowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] PCMCIA bugfixes
Date: Wed, 10 Nov 2010 14:36:57 +0100 [thread overview]
Message-ID: <20101110133657.GA22986@comet.dominikbrodowski.net> (raw)
Hey,
in order to address a few -- mostly minor -- issues, I intend to push these
changes shortly. They're available at
git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git urgent
As usual, I'm interested in your input to this patch series. The individual
patches will be sent out (at least) to the PCMCIA list in a few moments.
Best,
Dominik
Andres Salomon (1):
pcmcia: fix warning in synclink driver
Joe Perches (1):
drivers/pcmcia/soc_common.c: Use printf extension %pV
Komuro (1):
pd6729: Coding Style fixes
Nicolas Kaiser (1):
pcmcia/cm4000: fix error code
Uwe Kleine-K?nig (1):
pcmcia/sa1100: don't put machine specific init functions in .init.text
drivers/char/pcmcia/cm4000_cs.c | 3 ++-
drivers/char/pcmcia/synclink_cs.c | 1 +
drivers/pcmcia/pd6729.c | 8 ++++----
drivers/pcmcia/pd6729.h | 2 +-
drivers/pcmcia/pxa2xx_sharpsl.c | 2 +-
drivers/pcmcia/sa1100_assabet.c | 2 +-
drivers/pcmcia/sa1100_cerf.c | 2 +-
drivers/pcmcia/sa1100_generic.c | 2 +-
drivers/pcmcia/sa1100_h3600.c | 2 +-
drivers/pcmcia/sa1100_shannon.c | 2 +-
drivers/pcmcia/sa1100_simpad.c | 2 +-
drivers/pcmcia/soc_common.c | 9 +++++++--
12 files changed, 22 insertions(+), 15 deletions(-)
next reply other threads:[~2010-11-10 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 13:36 Dominik Brodowski [this message]
2010-11-10 13:37 ` [PATCH 3/5] pcmcia/sa1100: don't put machine specific init functions in .init.text Dominik Brodowski
2010-11-10 13:37 ` [PATCH 5/5] drivers/pcmcia/soc_common.c: Use printf extension %pV Dominik Brodowski
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=20101110133657.GA22986@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).