linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jic23@cam.ac.uk (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] pxa2xx related pcmcia tidyups.
Date: Wed, 13 Jul 2011 15:54:55 +0100	[thread overview]
Message-ID: <1310568898-9201-1-git-send-email-jic23@cam.ac.uk> (raw)

Big one here is that 10 drivers don't do anything for socket_init and
socket_suspend.  That would suggest making them optional?

The other patch is a trivial cleanup of the one device I actually have.

Thanks,

Jonathan

Jonathan Cameron (3):
  drivers:pcmcia:soc_common:  make socket_init and socket_suspend
    optional
  pcmcia: pxa2xx: remove empty socket_init / socket_resume functions.
  pxa2xx pcmcia - stargate 2 use gpio array.

 drivers/pcmcia/pxa2xx_balloon3.c  |   10 ----------
 drivers/pcmcia/pxa2xx_cm_x255.c   |   11 -----------
 drivers/pcmcia/pxa2xx_cm_x270.c   |   11 -----------
 drivers/pcmcia/pxa2xx_colibri.c   |   11 -----------
 drivers/pcmcia/pxa2xx_mainstone.c |   10 ----------
 drivers/pcmcia/pxa2xx_palmld.c    |   11 -----------
 drivers/pcmcia/pxa2xx_palmtc.c    |   11 -----------
 drivers/pcmcia/pxa2xx_palmtx.c    |   11 -----------
 drivers/pcmcia/pxa2xx_stargate2.c |   34 +++++++++++-----------------------
 drivers/pcmcia/pxa2xx_viper.c     |   10 ----------
 drivers/pcmcia/soc_common.c       |    7 ++++---
 11 files changed, 15 insertions(+), 122 deletions(-)

-- 
1.7.3.4

             reply	other threads:[~2011-07-13 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 14:54 Jonathan Cameron [this message]
2011-07-13 14:54 ` [PATCH 1/3] drivers:pcmcia:soc_common: make socket_init and socket_suspend optional Jonathan Cameron
2011-07-13 14:54 ` [PATCH 2/3] pcmcia: pxa2xx: remove empty socket_init / socket_resume functions Jonathan Cameron
2011-07-13 14:54 ` [PATCH 3/3] pxa2xx pcmcia - stargate 2 use gpio array Jonathan Cameron
2011-07-29 16:00 ` [PATCH 0/3] pxa2xx related pcmcia tidyups 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=1310568898-9201-1-git-send-email-jic23@cam.ac.uk \
    --to=jic23@cam.ac.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).