From: Greg KH <gregkh@linuxfoundation.org>
To: Valentina Manea <valentina.manea.m@gmail.com>
Cc: "Tülin İzer" <tulinizer@gmail.com>,
"Alan Stern" <stern@rowland.harvard.edu>,
mail@beyermatthias.de, hdegoede@redhat.com,
"Federico Manzan" <f.manzan@gmail.com>,
"Kurt Garloff" <kurt@garloff.de>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
"Linux Kernel Community @ ROSEdu" <firefly@lists.rosedu.org>,
"Andy Grover" <andy.grover@gmail.com>,
max@vozeler.com
Subject: Re: [PATCH 0/3] usbip: move usbip out of staging
Date: Thu, 7 Aug 2014 13:16:00 -0700 [thread overview]
Message-ID: <20140807201600.GA5720@kroah.com> (raw)
In-Reply-To: <CABdoFFd9ZuikFyaSfOyn-babECtno50_GGNHofK1-LmhLCqeTw@mail.gmail.com>
On Thu, Aug 07, 2014 at 12:36:06PM -0700, Valentina Manea wrote:
> On Wed, Aug 6, 2014 at 10:33 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Thu, Aug 07, 2014 at 08:10:25AM +0300, Valentina Manea wrote:
> >> This is a resend of the patch series from March.
> >>
> >> After migrating userspace code to libudev, converting usbip-host
> >> to a device driver and various bug fixes and enhancements, USB/IP
> >> is fully functional and can be moved out of staging.
> >>
> >> This patch series moves it as following:
> >> * userspace code to tools/usb/usbip
> >> * kernel code to drivers/usb/usbip
> >>
> >> Besides this, a warning generated in the kernel code is solved.
> >
> > What kernel version is this against?
> >
>
> I rebased my tree against master in the staging tree.
Great, thanks.
> > And can we get a maintainer for this code? I don't want to see it sit
> > "ownerless" in the kernel tree. Will you be willing to do this?
> >
>
> Yes. But I should be briefed about that responsibilities will this involve.
The top of the MAINTAINERS should have this information, look in the S:
Status section about what type of category you are in.
Basically I'd like you to be the one to handle patches that are sent in
for the code, just by reviewing them, you don't have to send them on to
me if you don't want to (some usb subsystem maintainers do do this, like
for usb-serial and xhci), it's up to you.
Also, any bug reports or questions about the code would come to you
first, along with the rest of the linux-usb@vger developers, you aren't
alone in this at all.
Does that help explain things better?
greg k-h
next prev parent reply other threads:[~2014-08-07 20:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 5:10 [PATCH 0/3] usbip: move usbip out of staging Valentina Manea
2014-08-07 5:10 ` Valentina Manea
2014-08-07 5:10 ` [PATCH 1/3] usbip: move usbip userspace code " Valentina Manea
2014-08-07 5:10 ` [PATCH 2/3] usbip: move usbip kernel " Valentina Manea
2014-08-19 18:38 ` Greg KH
2014-08-20 3:21 ` Valentina Manea
2014-08-20 4:02 ` Greg KH
2014-08-07 5:10 ` [PATCH 3/3] usbip: remove struct usb_device_id table Valentina Manea
2014-08-07 5:33 ` [PATCH 0/3] usbip: move usbip out of staging Greg KH
2014-08-07 19:36 ` Valentina Manea
2014-08-07 19:48 ` Shuah Khan
2014-08-07 20:16 ` Greg KH [this message]
2014-08-09 4:41 ` Valentina Manea
2014-08-09 14:17 ` Greg KH
2014-08-11 13:38 ` Shuah Khan
-- strict thread matches above, loose matches on Subject: below --
2014-03-18 20:11 Valentina Manea
2014-03-18 20:20 ` Joe Perches
2014-03-18 20:33 ` Greg KH
2014-08-06 12:22 ` Max Vozeler
2014-08-06 14:45 ` Greg KH
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=20140807201600.GA5720@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.grover@gmail.com \
--cc=f.manzan@gmail.com \
--cc=firefly@lists.rosedu.org \
--cc=hdegoede@redhat.com \
--cc=kurt@garloff.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mail@beyermatthias.de \
--cc=max@vozeler.com \
--cc=stern@rowland.harvard.edu \
--cc=tulinizer@gmail.com \
--cc=valentina.manea.m@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox