All of lore.kernel.org
 help / color / mirror / Atom feed
From: robin@protonic.nl (Robin van der Gracht)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] move ARM LCD display driver to auxdisplay
Date: Thu, 12 May 2016 12:25:00 +0200	[thread overview]
Message-ID: <20160512122500.11411882@erd979> (raw)
In-Reply-To: <CACRpkdZwPVMx-dXVkfVwFN0juzVuyvShV7yDWbUFSXOPE=uUrw@mail.gmail.com>

On Mon, 9 May 2016 16:27:00 +0200
Linus Walleij <linus.walleij@linaro.org> wrote:

> On Mon, May 9, 2016 at 4:17 PM, Robin van der Gracht
> <robin@protonic.nl> wrote:
> > On Mon, 9 May 2016 15:19:26 +0200
> > Linus Walleij <linus.walleij@linaro.org> wrote:
> >  
> >> On Mon, May 9, 2016 at 9:06 AM, Robin van der Gracht
> >> <robin@protonic.nl> wrote:
> >>  
> >> > If you guys feel like auxdisplay is not the right subsystem for
> >> > the driver, and would like me to move it, please share.  
> >>
> >> The best would be if you volunteer to maintain it and bring
> >> it forward.  
> >
> > Thats fine. Would it suffice if I submit another patch adding myself
> > to the maintainers file?  
> 
> That's half of it, if Miguel does not come back then his name
> should be removed as the second step.
> 

First half is completed. I've added myself as maintainer for the
driver I've posted recently (HT16K33 LED CONTROLLER DRIVER).

According to MAINTAINERS, Miguel maintains:
 - CFAG12864B LCD DRIVER
 - CFAG12864BFB LCD FRAMEBUFFER DRIVER
 - KS0108 LCD CONTROLLER DRIVER
 - AUXILIARY DISPLAY DRIVERS

AFAIK, I should not be judge in Miguels case.

@linus: I'll send my patches to Greg if you agree on this.

Kind regards,
Robin van der Gracht

WARNING: multiple messages have this Message-ID (diff)
From: Robin van der Gracht <robin@protonic.nl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	"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: Thu, 12 May 2016 12:25:00 +0200	[thread overview]
Message-ID: <20160512122500.11411882@erd979> (raw)
In-Reply-To: <CACRpkdZwPVMx-dXVkfVwFN0juzVuyvShV7yDWbUFSXOPE=uUrw@mail.gmail.com>

On Mon, 9 May 2016 16:27:00 +0200
Linus Walleij <linus.walleij@linaro.org> wrote:

> On Mon, May 9, 2016 at 4:17 PM, Robin van der Gracht
> <robin@protonic.nl> wrote:
> > On Mon, 9 May 2016 15:19:26 +0200
> > Linus Walleij <linus.walleij@linaro.org> wrote:
> >  
> >> On Mon, May 9, 2016 at 9:06 AM, Robin van der Gracht
> >> <robin@protonic.nl> wrote:
> >>  
> >> > If you guys feel like auxdisplay is not the right subsystem for
> >> > the driver, and would like me to move it, please share.  
> >>
> >> The best would be if you volunteer to maintain it and bring
> >> it forward.  
> >
> > Thats fine. Would it suffice if I submit another patch adding myself
> > to the maintainers file?  
> 
> That's half of it, if Miguel does not come back then his name
> should be removed as the second step.
> 

First half is completed. I've added myself as maintainer for the
driver I've posted recently (HT16K33 LED CONTROLLER DRIVER).

According to MAINTAINERS, Miguel maintains:
 - CFAG12864B LCD DRIVER
 - CFAG12864BFB LCD FRAMEBUFFER DRIVER
 - KS0108 LCD CONTROLLER DRIVER
 - AUXILIARY DISPLAY DRIVERS

AFAIK, I should not be judge in Miguels case.

@linus: I'll send my patches to Greg if you agree on this.

Kind regards,
Robin van der Gracht

  parent reply	other threads:[~2016-05-12 10:25 UTC|newest]

Thread overview: 32+ 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-23  9:43 ` Linus Walleij
2016-04-25 11:57 ` Maxime Ripard
2016-04-25 11:57   ` Maxime Ripard
2016-04-25 22:18   ` Arnd Bergmann
2016-04-25 22:18     ` Arnd Bergmann
2016-04-26 10:41   ` Linus Walleij
2016-04-26 10:41     ` Linus Walleij
2016-04-28  9:26     ` Maxime Ripard
2016-04-28  9:26       ` Maxime Ripard
2016-04-29  7:49       ` Linus Walleij
2016-04-29  7:49         ` Linus Walleij
2016-04-29 14:53       ` Tomi Valkeinen
2016-04-29 14:53         ` Tomi Valkeinen
2016-05-09  7:06         ` Robin van der Gracht
2016-05-09  7:06           ` Robin van der Gracht
2016-05-09 13:19           ` Linus Walleij
2016-05-09 13:19             ` Linus Walleij
2016-05-09 14:17             ` Robin van der Gracht
2016-05-09 14:17               ` Robin van der Gracht
2016-05-09 14:27               ` Linus Walleij
2016-05-09 14:27                 ` Linus Walleij
2016-05-10  7:10                 ` Greg KH
2016-05-10  7:10                   ` Greg KH
2016-05-11  7:46                   ` Robin van der Gracht
2016-05-11  7:46                     ` Robin van der Gracht
2016-05-11  8:34                     ` Greg KH
2016-05-11  8:34                       ` Greg KH
2016-05-12 10:25                 ` Robin van der Gracht [this message]
2016-05-12 10:25                   ` Robin van der Gracht
2016-05-18 14:35                   ` Linus Walleij
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=20160512122500.11411882@erd979 \
    --to=robin@protonic.nl \
    --cc=linux-arm-kernel@lists.infradead.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.