From: Heiko Stuebner <heiko@sntech.de>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] video: fbdev: remove unused auo_k190xfb drivers
Date: Fri, 27 Apr 2018 15:07:41 +0000 [thread overview]
Message-ID: <3959140.hnfON7x99k@phil> (raw)
In-Reply-To: <6386409.PTMV4p8OHo@amdc3058>
Am Freitag, 27. April 2018, 13:04:24 CEST schrieb Bartlomiej Zolnierkiewicz:
> auo_k1900fb and auo_k1901fb drivers have been introduced six
> years ago by following commits:
>
> commit 2c8304d3125b ("video: auo_k190x: add code shared by controller drivers")
> commit 96b1d500e028 ("video: auo_k190x: add driver for AUO-K1900 variant")
> commit 53027cdf2a67 ("video: auo_k190x: add driver for AUO-K1901 variant")
>
> They never had any in-kernel user so just remove them (since
> they are platform drivers they need corresponding platform
> devices to be registered by kernel and it has never happened).
>
> Cc: Heiko Stübner <heiko@sntech.de>
> Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
While I still hold the ereaders using these controllers in high regard
as my first kernel hacking project, reality is that I don't think I'll
ever continue on trying to mainline these and if later someone wants
to resurrect these (very old now) devices, they'll probably need a drm-
driver anyway. So for the removal
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Heiko
next prev parent reply other threads:[~2018-04-27 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180427110425eucas1p12aca3b573a6c3fc4b51da9d5d34b3cec@eucas1p1.samsung.com>
2018-04-27 11:04 ` [PATCH] video: fbdev: remove unused auo_k190xfb drivers Bartlomiej Zolnierkiewicz
2018-04-27 15:07 ` Heiko Stuebner [this message]
2018-05-14 13:39 ` Bartlomiej Zolnierkiewicz
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=3959140.hnfON7x99k@phil \
--to=heiko@sntech.de \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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 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).