All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Joe Perches <joe@perches.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: fix entry of char/misc
Date: Tue, 13 Oct 2015 10:39:47 -0700	[thread overview]
Message-ID: <20151013173947.GA8886@kroah.com> (raw)
In-Reply-To: <20151013171924.GB6720@sudip-pc>

On Tue, Oct 13, 2015 at 10:49:24PM +0530, Sudip Mukherjee wrote:
> On Tue, Oct 13, 2015 at 07:48:05AM -0700, Joe Perches wrote:
> > On Tue, 2015-10-13 at 15:34 +0530, Sudip Mukherjee wrote:
> > > Greg and Arnd are supporter of char and misc drivers. While using
> > > getmaintainer.pl on any patch or any file in these directories their
> > > names were never displayed.
> > []
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > []
> > >  M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > >  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> > >  S:	Supported
> > > -F:	drivers/char/*
> > > -F:	drivers/misc/*
> > > +F:	drivers/char/
> > > +F:	drivers/misc/
> > >  F:	include/linux/miscdevice.h
> > 
> > Do Greg and Arnd really want to be supporting all
> > subsystems below drivers/char like agp and xillybus?
> 
> I don't know that. Maybe Greg and Arnd can say.
> But wasn't that the intention when char/* and misc/* was mentioned here?

Kind of, I'm here to pick up the portions of this tree that do not have
a maintainer already (random.c is one example.)

thanks,

greg k-h

  parent reply	other threads:[~2015-10-13 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 10:04 [PATCH] MAINTAINERS: fix entry of char/misc Sudip Mukherjee
2015-10-13 14:48 ` Joe Perches
2015-10-13 17:19   ` Sudip Mukherjee
2015-10-13 17:35     ` Joe Perches
2015-10-13 17:39     ` Greg Kroah-Hartman [this message]
2015-10-14  4:48       ` Sudip Mukherjee

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=20151013173947.GA8886@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.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 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.