From: Arnd Bergmann <arnd@arndb.de>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"arm@kernel.org" <arm@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Miguel Ojeda Sandonis <maxextreme@gmail.com>
Subject: Re: [GIT PULL] move ARM LCD display driver to auxdisplay
Date: Tue, 26 Apr 2016 00:18:45 +0200 [thread overview]
Message-ID: <8373519.0RWpCDubQ0@wuerfel> (raw)
In-Reply-To: <20160425115758.GA4874@lukather>
On Monday 25 April 2016 13:57:58 Maxime Ripard wrote:
> Hi,
>
> On Sat, Apr 23, 2016 at 11:43:58AM +0200, Linus Walleij wrote:
> > Hi ARM SoC guys,
> >
> > these two patches move the ARM character LCD driver from
> > misc drivers to the auxdisplay subsystem where it belongs and
> > updates the defconfig for the RealView accordingly.
> >
> > Please pull it into some cleanup branch in the ARM SoC
> > tree.
> >
> > I tried to get some ACK from the auxdisplay maintainer but no
> > reaction.
>
> Auxdisplay is not a new framework, but rather a very old one.
>
> It got introduced in 2.6.21, and only received a couple of drivers
> since.
>
> It seems to be quite redundant with fbdev deferred_io, which itself is
> almost deprecated these days.
I'm holding off on this pull request for now then.
I'd certainly like to see the driver get moved out of drivers/misc,
let me know once there has been an agreement of where it should go.
Arnd
next prev parent reply other threads:[~2016-04-25 22:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 9:43 [GIT PULL] move ARM LCD display driver to auxdisplay Linus Walleij
2016-04-25 11:57 ` Maxime Ripard
2016-04-25 22:18 ` Arnd Bergmann [this message]
2016-04-26 10:41 ` Linus Walleij
2016-04-28 9:26 ` Maxime Ripard
2016-04-29 7:49 ` Linus Walleij
2016-04-29 14:53 ` Tomi Valkeinen
2016-05-09 7:06 ` Robin van der Gracht
2016-05-09 13:19 ` Linus Walleij
2016-05-09 14:17 ` Robin van der Gracht
2016-05-09 14:27 ` Linus Walleij
2016-05-10 7:10 ` Greg KH
2016-05-11 7:46 ` Robin van der Gracht
2016-05-11 8:34 ` Greg KH
2016-05-12 10:25 ` Robin van der Gracht
2016-05-18 14:35 ` Linus Walleij
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=8373519.0RWpCDubQ0@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxextreme@gmail.com \
--cc=maxime.ripard@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox