From: Shuah Khan <shuahkh@osg.samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: davem@davemloft.net, geert+renesas@glider.be, mchehab@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] MAINTAINERS: Add bugzilla and documentation entites for kselftest, usbip
Date: Thu, 20 Apr 2017 09:57:15 -0600 [thread overview]
Message-ID: <6786512b-7b9c-e0e4-3a66-676a6b910f76@osg.samsung.com> (raw)
In-Reply-To: <20170420155208.GA6935@kroah.com>
On 04/20/2017 09:52 AM, Greg KH wrote:
> On Thu, Apr 20, 2017 at 09:50:10AM -0600, Shuah Khan wrote:
>> @@ -13033,6 +13035,8 @@ M: Valentina Manea <valentina.manea.m@gmail.com>
>> M: Shuah Khan <shuahkh@osg.samsung.com>
>> M: Shuah Khan <shuah@kernel.org>
>> L: linux-usb@vger.kernel.org
>> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
>> +B: https://bugzilla.kernel.org
>> S: Maintained
>> F: Documentation/usb/usbip_protocol.txt
>> F: drivers/usb/usbip/
>
> I don't like USB bugs in bugzilla at all, how are you going to separate
> the usbip bugs out from the rest of the usb bugs there?
>
I didn't realize usb bugs aren't tracked in bugzilla. I quick search
would have told me that - my bad. My thinking is that we could use a
Tag for USB/IP. However, it could get messy.
I will resend the patch to just add the git entry which would be
helpful since you take these patches through your usb tree.
thanks,
-- Shuah
prev parent reply other threads:[~2017-04-20 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 15:50 Shuah Khan
2017-04-20 15:52 ` Greg KH
2017-04-20 15:57 ` Shuah Khan [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=6786512b-7b9c-e0e4-3a66-676a6b910f76@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mchehab@kernel.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
all inboxes | Powered by JetHome®