From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: Jean Delvare <jdelvare@suse.de>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH 0/3] i2c: for next API conversion, remove parport-light driver
Date: Mon, 13 Jan 2020 22:06:40 +0100 [thread overview]
Message-ID: <20200113210643.5033-1-wsa+renesas@sang-engineering.com> (raw)
When checking how to convert i2c_setup_smbus_alert() to return ERRPTRs,
I decided it makes more sense to remove the parport-light driver than to
convert it. The justifications for its existance do not hold anymore
IMO. People can/should switch to the parport driver if needed.
And this led to some other minor updates to the parport driver. Only
build tested.
Opinions?
Wolfram Sang (3):
i2c: parport-light: remove driver
i2c: parport: simplify Kconfig description
i2c: parport: move include file into main source
.../i2c/busses/i2c-parport-light.rst | 24 --
Documentation/i2c/busses/index.rst | 1 -
MAINTAINERS | 2 -
drivers/i2c/busses/Kconfig | 38 +--
drivers/i2c/busses/Makefile | 1 -
drivers/i2c/busses/i2c-parport-light.c | 267 ------------------
drivers/i2c/busses/i2c-parport.c | 100 ++++++-
drivers/i2c/busses/i2c-parport.h | 106 -------
8 files changed, 101 insertions(+), 438 deletions(-)
delete mode 100644 Documentation/i2c/busses/i2c-parport-light.rst
delete mode 100644 drivers/i2c/busses/i2c-parport-light.c
delete mode 100644 drivers/i2c/busses/i2c-parport.h
--
2.20.1
next reply other threads:[~2020-01-13 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 21:06 Wolfram Sang [this message]
2020-01-13 21:06 ` [PATCH 1/3] i2c: parport-light: remove driver Wolfram Sang
2020-01-15 11:04 ` Jean Delvare
2020-01-15 17:26 ` Wolfram Sang
2020-01-13 21:06 ` [PATCH 2/3] i2c: parport: simplify Kconfig description Wolfram Sang
2020-01-15 11:07 ` Jean Delvare
2020-01-15 17:26 ` Wolfram Sang
2020-01-13 21:06 ` [PATCH 3/3] i2c: parport: move include file into main source Wolfram Sang
2020-01-15 14:17 ` Jean Delvare
2020-01-15 17:26 ` 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=20200113210643.5033-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.