From: Petko Manolov <petkan@nucleusys.com>
To: joe@perches.com
Cc: linux-usb-devel@lists.sourceforge.net,
petkan@users.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] [504/2many] MAINTAINERS - USB PEGASUS DRIVER
Date: Mon, 13 Aug 2007 15:55:14 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708131553290.14743@bender.nucleusys.com> (raw)
In-Reply-To: <46bffc64.Are6NTp/45DX6lxZ%joe@perches.com>
On Sun, 12 Aug 2007, joe@perches.com wrote:
> Add file pattern to MAINTAINER entry
>
> Signed-off-by: Joe Perches <joe@perches.com>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d822865..fc87fa7 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4764,6 +4764,7 @@ L: linux-usb-devel@lists.sourceforge.net
> L: netdev@vger.kernel.org
> W: http://pegasus2.sourceforge.net/
> S: Maintained
> +F: drivers/net/usb/pegasus.*
>
> USB PRINTER DRIVER (usblp)
> P: Pete Zaitcev
>
Well, what can i say? "NO, don't do it!" is probably not going to work so
i assume i will have to ACK. :-)
Petko
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
prev parent reply other threads:[~2007-08-13 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:38 [PATCH] [504/2many] MAINTAINERS - USB PEGASUS DRIVER joe
2007-08-13 12:55 ` Petko Manolov [this message]
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=Pine.LNX.4.64.0708131553290.14743@bender.nucleusys.com \
--to=petkan@nucleusys.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=petkan@users.sourceforge.net \
--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