From: Randy Dunlap <randy.dunlap@oracle.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Steven Noonan <steven@uplinklabs.net>,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: make MAINTAINERS slightly easier to search
Date: Thu, 02 Oct 2008 15:32:20 -0700 [thread overview]
Message-ID: <48E54BF4.3000600@oracle.com> (raw)
In-Reply-To: <20081002222003.GA1857@elf.ucw.cz>
Pavel Machek wrote:
> On Thu 2008-10-02 08:58:20, Randy Dunlap wrote:
>> On Thu, 2 Oct 2008 02:08:20 -0700 Steven Noonan wrote:
>>
>>> On Thu, Oct 2, 2008 at 1:14 AM, Pavel Machek <pavel@suse.cz> wrote:
>>>> ...shall we add rule that subsystems will have "subsystem" in the name
>>>> so that search does not list all the drivers, first?
>>>>
>>>> Signed-off-by: Pavel Machek <pavel@suse.cz>
>>>> Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
>>>>
>>>>
>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>> index 3596d17..7345707 100644
>>>> --- a/MAINTAINERS
>>>> +++ b/MAINTAINERS
>>>> @@ -3825,7 +3825,7 @@ L: linux-kernel@vger.kernel.org
>>>> W: http://tifmxx.berlios.de/
>>>> S: Maintained
>>>>
>>>> -SOUND
>>>> +SOUND SUBSYSTEM (ADVANCED LINUX SOUND SYSTEM, ALSA)
>>> Advanced Linux Sound System = ALSS? How about switching it to
>>> 'ADVANCED LINUX SOUND ARCHITECTURE', which fits the original acronym?
>>> :)
>> Yes, concur. Thanks.
>
> Fixed in my tree. Who is maintainer of MAINTAINERS file? ;-).
I would expect Andrew to merge it.
If he doesn't, then I'll try to merge it. :)
~Randy
next prev parent reply other threads:[~2008-10-02 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 8:14 make MAINTAINERS slightly easier to search Pavel Machek
2008-10-02 9:08 ` Steven Noonan
2008-10-02 15:58 ` Randy Dunlap
2008-10-02 22:20 ` Pavel Machek
2008-10-02 22:32 ` Randy Dunlap [this message]
2008-10-16 10:02 ` Pavel Machek
2008-10-16 14:30 ` Randy Dunlap
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=48E54BF4.3000600@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=steven@uplinklabs.net \
/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.