All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] move ARM LCD display driver to auxdisplay
Date: Tue, 10 May 2016 09:10:04 +0200	[thread overview]
Message-ID: <20160510071004.GA7318@kroah.com> (raw)
In-Reply-To: <CACRpkdZwPVMx-dXVkfVwFN0juzVuyvShV7yDWbUFSXOPE=uUrw@mail.gmail.com>

On Mon, May 09, 2016 at 04:27:00PM +0200, Linus Walleij 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.
> 
> You also need to have an idea on a path to funnel accumulated
> patches upstream to Torvalds. The recent patches to this
> subsystem were funneled by Greg, so we should ask him how
> he prefer to proceed.
> 
> Greg, what do you prefer?

I don't care :)

I can keep doing this, sending stuff to Linus through my char/misc tree,
or it can go through someone else's tree, it doesn't bother me...

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Robin van der Gracht <robin@protonic.nl>,
	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: Tue, 10 May 2016 09:10:04 +0200	[thread overview]
Message-ID: <20160510071004.GA7318@kroah.com> (raw)
In-Reply-To: <CACRpkdZwPVMx-dXVkfVwFN0juzVuyvShV7yDWbUFSXOPE=uUrw@mail.gmail.com>

On Mon, May 09, 2016 at 04:27:00PM +0200, Linus Walleij 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.
> 
> You also need to have an idea on a path to funnel accumulated
> patches upstream to Torvalds. The recent patches to this
> subsystem were funneled by Greg, so we should ask him how
> he prefer to proceed.
> 
> Greg, what do you prefer?

I don't care :)

I can keep doing this, sending stuff to Linus through my char/misc tree,
or it can go through someone else's tree, it doesn't bother me...

thanks,

greg k-h

  reply	other threads:[~2016-05-10  7:10 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 [this message]
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
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=20160510071004.GA7318@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --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.