From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH 1/3] i2c: parport-light: remove driver
Date: Wed, 15 Jan 2020 12:04:47 +0100 [thread overview]
Message-ID: <20200115120447.1596a6ce@endymion> (raw)
In-Reply-To: <20200113210643.5033-2-wsa+renesas@sang-engineering.com>
On Mon, 13 Jan 2020 22:06:41 +0100, Wolfram Sang wrote:
> The justification of a light version of the parport driver was less
> overhead for embedded systems. Well, today, even if an embedded system
> still has a parport, it surely can handle the fully-fledged parport
> driver. Remove it to reduce the maintenance burden.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> .../i2c/busses/i2c-parport-light.rst | 24 --
> Documentation/i2c/busses/index.rst | 1 -
> MAINTAINERS | 2 -
> drivers/i2c/busses/Kconfig | 28 --
> drivers/i2c/busses/Makefile | 1 -
> drivers/i2c/busses/i2c-parport-light.c | 267 ------------------
> 6 files changed, 323 deletions(-)
> delete mode 100644 Documentation/i2c/busses/i2c-parport-light.rst
> delete mode 100644 drivers/i2c/busses/i2c-parport-light.c
> (...)
Reviewed-by: Jean Delvare <jdelvare@suse.de>
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2020-01-15 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 21:06 [PATCH 0/3] i2c: for next API conversion, remove parport-light driver Wolfram Sang
2020-01-13 21:06 ` [PATCH 1/3] i2c: parport-light: remove driver Wolfram Sang
2020-01-15 11:04 ` Jean Delvare [this message]
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=20200115120447.1596a6ce@endymion \
--to=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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.