All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Lee Jones <lee.jones@linaro.org>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Jingoo Han <jingoohan1@gmail.com>,
	linux-fbdev@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-sh@vger.kernel.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>
Subject: Re: [RFC 0/4] gpio-backlight: remove platform data support
Date: Tue, 27 Mar 2018 11:59:04 +0000	[thread overview]
Message-ID: <CACRpkdbCqYF-OsmsHFrY5H56oS=FepVFJRqvCM7yj9Ox4E6SEA@mail.gmail.com> (raw)
In-Reply-To: <20180315224202.96668-1-dmitry.torokhov@gmail.com>

On Thu, Mar 15, 2018 at 11:41 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:

> This series attempts to remove platform data support from gpio_blackllist
> driver

We really need a GPIO blacklist driver in the kernel, but for
not let's fix backlight :D :D

> and switch it over to generic device properties/GPIO tables.

This series:
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

> Please note that I do not have the hardware (do we even care about
> ecovec24? I'd like to rip out platform data support from tsc2007 as
> well, but ecovec24 is using custom pendown handler and GPIOs have
> to be switched off from interrupt mode to GPIO and back in that
> pendown handler, which is all quite messy. If we do not care about
> this board I'd much rather removed that custom pendown).

I am also struggling with refactoring of board files, all over the place.
At least Arnd deleted the Blackfin stuff now, but the misc ARM board
and MIPS stuff still give me the creeps sometimes.

I guess if maintainers of the boards are not there to even ACK
patches we can propose patches to simply delete them.

Yours,
Linus Walleij

WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Lee Jones <lee.jones@linaro.org>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Jingoo Han <jingoohan1@gmail.com>,
	linux-fbdev@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-sh@vger.kernel.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>
Subject: Re: [RFC 0/4] gpio-backlight: remove platform data support
Date: Tue, 27 Mar 2018 13:59:04 +0200	[thread overview]
Message-ID: <CACRpkdbCqYF-OsmsHFrY5H56oS=FepVFJRqvCM7yj9Ox4E6SEA@mail.gmail.com> (raw)
In-Reply-To: <20180315224202.96668-1-dmitry.torokhov@gmail.com>

On Thu, Mar 15, 2018 at 11:41 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:

> This series attempts to remove platform data support from gpio_blackllist
> driver

We really need a GPIO blacklist driver in the kernel, but for
not let's fix backlight :D :D

> and switch it over to generic device properties/GPIO tables.

This series:
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

> Please note that I do not have the hardware (do we even care about
> ecovec24? I'd like to rip out platform data support from tsc2007 as
> well, but ecovec24 is using custom pendown handler and GPIOs have
> to be switched off from interrupt mode to GPIO and back in that
> pendown handler, which is all quite messy. If we do not care about
> this board I'd much rather removed that custom pendown).

I am also struggling with refactoring of board files, all over the place.
At least Arnd deleted the Blackfin stuff now, but the misc ARM board
and MIPS stuff still give me the creeps sometimes.

I guess if maintainers of the boards are not there to even ACK
patches we can propose patches to simply delete them.

Yours,
Linus Walleij

  parent reply	other threads:[~2018-03-27 11:59 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 22:41 [RFC 0/4] gpio-backlight: remove platform data support Dmitry Torokhov
2018-03-15 22:41 ` Dmitry Torokhov
2018-03-15 22:41 ` [RFC 1/4] backlight: gpio_backlight: use generic device properties Dmitry Torokhov
2018-03-15 22:41   ` Dmitry Torokhov
2018-03-27 11:53   ` Linus Walleij
2018-03-27 11:53     ` Linus Walleij
2018-03-15 22:42 ` [RFC 2/4] sh: ecovec24: conditionally register backlight device Dmitry Torokhov
2018-03-15 22:42   ` Dmitry Torokhov
2018-03-16 10:07   ` jacopo mondi
2018-03-16 10:07     ` jacopo mondi
2018-03-16 23:38     ` Dmitry Torokhov
2018-03-16 23:38       ` Dmitry Torokhov
2018-03-17  9:25       ` jacopo mondi
2018-03-17  9:25         ` jacopo mondi
2018-03-17 10:21         ` John Paul Adrian Glaubitz
2018-03-17 10:21           ` John Paul Adrian Glaubitz
2018-03-17 17:16           ` Rich Felker
2018-03-17 17:16             ` Rich Felker
2018-03-17 17:33             ` Dmitry Torokhov
2018-03-17 17:33               ` Dmitry Torokhov
2018-03-17 17:55             ` John Paul Adrian Glaubitz
2018-03-17 17:55               ` John Paul Adrian Glaubitz
2018-03-18 10:54           ` jacopo mondi
2018-03-18 10:54             ` jacopo mondi
2018-03-18 11:12             ` John Paul Adrian Glaubitz
2018-03-18 11:12               ` John Paul Adrian Glaubitz
2018-03-17 17:37         ` Dmitry Torokhov
2018-03-17 17:37           ` Dmitry Torokhov
2018-03-15 22:42 ` [RFC 3/4] sh: ecovec24: convert backlight to use device properties Dmitry Torokhov
2018-03-15 22:42   ` Dmitry Torokhov
2018-03-16  8:50   ` Geert Uytterhoeven
2018-03-16  8:50     ` Geert Uytterhoeven
2018-03-16 23:40     ` Dmitry Torokhov
2018-03-16 23:40       ` Dmitry Torokhov
2018-03-16 10:08   ` jacopo mondi
2018-03-16 10:08     ` jacopo mondi
2018-03-15 22:42 ` [RFC 4/4] backlight: gpio_backlight: remove platform data support Dmitry Torokhov
2018-03-15 22:42   ` Dmitry Torokhov
2018-03-27 11:55   ` Linus Walleij
2018-03-27 11:55     ` Linus Walleij
2018-03-16 11:11 ` [RFC 0/4] gpio-backlight: " Daniel Thompson
2018-03-27 11:59 ` Linus Walleij [this message]
2018-03-27 11:59   ` 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='CACRpkdbCqYF-OsmsHFrY5H56oS=FepVFJRqvCM7yj9Ox4E6SEA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=dalias@libc.org \
    --cc=daniel.thompson@linaro.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jingoohan1@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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.