lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 7 Aug 2014 13:16:00 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Valentina Manea <valentina.manea.m@...il.com>
Cc:	Tülin İzer <tulinizer@...il.com>,
	Alan Stern <stern@...land.harvard.edu>, mail@...ermatthias.de,
	hdegoede@...hat.com, Federico Manzan <f.manzan@...il.com>,
	Kurt Garloff <kurt@...loff.de>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	"Linux Kernel Community @ ROSEdu" <firefly@...ts.rosedu.org>,
	Andy Grover <andy.grover@...il.com>, max@...eler.com
Subject: Re: [PATCH 0/3] usbip: move usbip out of staging

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@...uxfoundation.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@...r developers, you aren't
alone in this at all.

Does that help explain things better?

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists