public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Greg KH <greg@kroah.com>
Cc: Jim Cromie <jim.cromie@gmail.com>,
	linux-kernel@vger.kernel.org, rpjday@crashcourse.ca,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH] fix bogus use of rc = alloc_chrdev_region()
Date: Tue, 14 Jun 2011 16:07:02 +0200	[thread overview]
Message-ID: <201106141607.02171.arnd@arndb.de> (raw)
In-Reply-To: <20110610204403.GA13450@kroah.com>

On Friday 10 June 2011, Greg KH wrote:
> On Fri, Jun 10, 2011 at 02:29:42PM -0600, Jim Cromie wrote:
> > can someone pick this up,
> > for this release or next ?
> 
> It was rumored that Arnd wanted to take over drivers/char/.

That's true. It probably means I should set up a tree now, before we get
too close to the next merge window.

On the topic of drivers/char/{nsc_gpio,pc8736x_gpio,scx200_gpio}, I wonder
if we should move them to drivers/gpio/nsc_gpio despite the fact that they
use a different (older) interface than all the other gpio drivers.

They have seen only a single non-janitor patch in the last five years,
so I don't think they will be a burden, but it might be nice to have them
in a place where people would actually look for them, with a comment that
they should be converted to the new API in order to be more useful.

	Arnd

  reply	other threads:[~2011-06-14 14:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1307079502-6326-1-git-send-email-jim.cromie@gmail.com>
2011-06-10 20:29 ` [PATCH] fix bogus use of rc = alloc_chrdev_region() Jim Cromie
2011-06-10 20:44   ` Greg KH
2011-06-14 14:07     ` Arnd Bergmann [this message]
2011-06-14 16:23       ` Grant Likely
2011-06-14 18:17         ` Arnd Bergmann
2011-06-14 18:23           ` Jim Cromie
2011-06-14 19:19           ` Grant Likely

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=201106141607.02171.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=grant.likely@secretlab.ca \
    --cc=greg@kroah.com \
    --cc=jim.cromie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    /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