From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Removing duplicate drivers from chips?
Date: Sun, 6 Sep 2009 22:55:26 +0200 [thread overview]
Message-ID: <20090906205526.GA8434@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
Hi Jean,
I am thinking about cleaning up the 'chips'-directory further by removing the
duplicate pca/pcf-drivers. Those are marked as deprecated for more than a year
now. Remembering the defconfig-discussion when we moved out the eeprom drivers,
I think it is best to not touch the defconfigs but inform the arch-maintainers
about the removal of these drivers, so they can handle whatever is necessary.
Are you okay with this approach or do you think we should keep the drivers a
little longer?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-09-06 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 20:55 Wolfram Sang [this message]
[not found] ` <20090906205526.GA8434-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-09-06 21:23 ` Removing duplicate drivers from chips? Jean Delvare
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=20090906205526.GA8434@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).