linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: linux-i2c@vger.kernel.org
Cc: linuxppc-dev@ozlabs.org, uclinux-dist-devel@blackfin.uclinux.org,
	linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org
Subject: Removing deprecated drivers from drivers/i2c/chips
Date: Wed,  9 Sep 2009 23:22:47 +0200	[thread overview]
Message-ID: <1252531371-14866-1-git-send-email-w.sang@pengutronix.de> (raw)

Hi,

continuing the quest to clean up and ultimately remove the drivers/i2c/chips
directory, this patch series removes three drivers for GPIO-expanders which are
obsoleted and marked as deprecated for more than a year. The newer (and better)
drivers can be found in drivers/gpio.

As it is ensured that the newer drivers cover the same i2c_device_ids, all
platform_devices will still match. Some defconfig updates may be necessary
though, but according to [1] this is left to the arch|platform-maintainers
(also as most defconfigs are quite outdated). For that reason, I put the
relevant arch-mailing-lists to Cc. Comments are welcome.

Regards,

   Wolfram

[1] http://lkml.org/lkml/2009/5/7/34

             reply	other threads:[~2009-09-09 21:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 21:22 Wolfram Sang [this message]
2009-09-09 21:22 ` [PATCH 1/4] gpio/pcf857x: copy i2c_device_id from old pcf8574-driver Wolfram Sang
2009-09-09 21:22 ` [PATCH 2/4] i2c/chips: Remove deprecated pcf8575-driver Wolfram Sang
2009-09-10 10:52   ` Bart Van Assche
2009-09-10 11:04     ` Wolfram Sang
2009-09-09 21:22 ` [PATCH 3/4] i2c/chips: Remove deprecated pca9539-driver Wolfram Sang
2009-09-09 23:28   ` Ben Gardner
2009-09-09 21:22 ` [PATCH 4/4] i2c/chips: Remove deprecated pcf8574-driver Wolfram Sang
2009-09-09 23:54 ` [Uclinux-dist-devel] Removing deprecated drivers from drivers/i2c/chips Mike Frysinger
2009-09-10  6:26   ` Wolfram Sang
2009-09-10  7:55     ` Mike Frysinger
2009-09-10 10:49 ` Jean Delvare
2009-09-10 11:07   ` Wolfram Sang

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=1252531371-14866-1-git-send-email-w.sang@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.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).