public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Joe Perches <joe@perches.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Pavel Machek <pavel@ucw.cz>,
	linux-pm@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [443/2many] MAINTAINERS - HIBERNATION (aka Software Suspend, aka swsusp):
Date: Tue, 14 Aug 2007 19:24:30 -0400	[thread overview]
Message-ID: <20070814232430.GA9325@redhat.com> (raw)
In-Reply-To: <20070814112237.a5f1e1a4.akpm@linux-foundation.org>

On Tue, Aug 14, 2007 at 11:22:37AM -0700, Andrew Morton wrote:
 > On Tue, 14 Aug 2007 11:15:41 -0700 (PDT)
 > Linus Torvalds <torvalds@linux-foundation.org> wrote:
 > 
 > > In other words, it would be much better to just have per-file markers, 
 > > along with some per-subdirectory stuff or similar.
 > 
 > And a `make maintainers' target to pull it all together..
 > 
 > (perhaps we could add a
 > 
 > 	maintainer <keyword>
 > 
 > record to Kconfig, then `make maintainers' goes and looks up <keyword>
 > somewhere and does something with it)

Not everything that's in MAINTAINERS has a Kconfig entry though,
so it really needs to live in the .c/.h files.

	Dave


-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-08-14 23:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  6:36 [PATCH] [443/2many] MAINTAINERS - HIBERNATION (aka Software Suspend, aka swsusp): joe
2007-08-13 14:18 ` Pavel Machek
2007-08-13 20:50 ` Rafael J. Wysocki
2007-08-13 20:54   ` Joe Perches
2007-08-13 21:25     ` Rafael J. Wysocki
2007-08-13 21:21       ` Joe Perches
2007-08-13 21:38         ` Rafael J. Wysocki
2007-08-14  7:05           ` Pavel Machek
2007-08-14 17:37             ` Rafael J. Wysocki
2007-08-14 17:57               ` Joe Perches
2007-08-14 18:14                 ` Rafael J. Wysocki
2007-08-14 18:15                 ` Linus Torvalds
2007-08-14 18:22                   ` Andrew Morton
2007-08-14 23:24                     ` Dave Jones [this message]
2007-08-15  2:51                       ` Kyle Moffett
2007-08-15 11:21                         ` Rafael J. Wysocki
2007-08-16 13:04                           ` Storing Maintainers info around the kernel tree Kyle Moffett
2007-08-16 15:13                             ` Rene Herman
2007-08-16 15:31                               ` [linux-pm] " Alan Stern
2007-08-16 15:50                                 ` Rene Herman
2007-08-16 21:39                                   ` Stefan Richter
2007-08-17  1:43                                     ` Rene Herman
2007-08-17  1:58                                       ` Alan Stern
2007-08-17  2:18                                         ` Rene Herman
2007-08-17  6:25                                           ` Stefan Richter
2007-08-14 18:25                   ` [PATCH] [443/2many] MAINTAINERS - HIBERNATION (aka Software Suspend, aka swsusp): Rene Herman
2007-08-14 18:42                   ` Joe Perches
2007-08-15  1:45                   ` Joe Perches

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=20070814232430.GA9325@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox